We need to be able to search our content by an attribute value, in this specific case by the ishcondition value. Is this possible in KC?
We need to be able to search our content by an attribute value, in this specific case by the ishcondition value. Is this possible in KC?
In case anyone at SDL is watching this (Dave De Meyer?), does anyone have the "full source XML syntax" to identify all the objects in the repository that have translation management disabled? (Enable Translation Management checkbox UNchecked).
In case anyone at SDL is watching this (Dave De Meyer?), does anyone have the "full source XML syntax" to identify all the objects in the repository that have translation management disabled? (Enable Translation Management checkbox UNchecked).
The above query was about finding content inside the xml objects, so inside the maps, topics and libraries. Your question is to find all repository objects that have a certain metadata field (FNOTRANSLATIONMGMT) set to the value FALSE. Some metadata fields are stored in the full-text-index to allow them to be "Searched".
Using ISHRemote with commandline: Get-IshTypeFieldDefinition | Out-GridView and then filtering to right field shows me
The Create-Read-Update-Search (CRUS) indicates if the field is passed for those object types to the full-text-index. And by the hyphen, you see it is not.
Now, the value is definitely stored in the relational-database part of the repository. The only way I can think of this morning is to use the API (or ISHRemote as a client of the API).Beware this could theoretically bring all logical back from your repository, so many Gigabytes or even Terrabytes of objects for some customers. You could also do something like described in https://community.sdl.com/developers-more/developers/tridiondocs-developers/f/livecontent_developer_forum/25832/getting-document-report-using-ishremote-api/80493#80493 and do a -FilterMetadata on the Get-IShDocumentObj ...
PS: the double negative field name FNOTRANSLATIONMGMT (with a NO in the field name) was even chosen before I started working with the software, I think we learned from that :-)