The organization of the data in your tenant is called the data model, and understanding this data model can help you create the most effective search queries.
There’s no info on how to search on a lot of nested objects.
Specifically I am looking for @accessModelMetadata which now applies to Entitlements.
But there are a lot of undocumented nested items:
Hey Remi! Thanks for bringing this to our attention. I actually just replied to your comment on the FAQs and Sample Data Models page, which it seems is about the same issue. We’ll address all of these in the same ticket: SAASDOCS-7920
For Search by Entitlements and Access Profiles, can you provide more details on what the value returned is recording for “modified” and “synced”? I could not find a reference to “synced” other than here. When testing in Sandbox, I see that the “modified” Date appears to be set to the last time the entitlement was aggregated, but the “synced” date seems to be the last refresh/latest date.
This could also be added to the Managing Entitlements section as well.
Hi Geoff! I’ve created SAASDOCS-8284 to review our search information for entitlements and access profiles. We’ll let you know when that work is completed. Thanks!
Thanks for getting this updated. I noticed that the Documentation now states that the “modified” can have the time portion set. Is this required? The Search only returns the date portion for this field, so if the time is required, that will not be obvious to the users. Could that be looked at and a note made as to what to expect with that?
Thanks for your feedback, @gmilunich! I’ve created a Jira ticket to address your question: SAASDOCS-8375
Just to make sure I understand your ask, it sounds like you aren’t sure whether the “time” in date-type fields such as modified is required. Do I understand you correctly?
that is correct. When the User views this in the UI, there is no time portion visible. If a time portion is required to be specified, the user would not know what should be specified there to get the results they desire.
ie: Suppose that there are 16 records returned as modified on 10/10/2024 in the search and the user wants to return those. Are they required to set the time portion? If so, does that then require them to use a Range Value, since adding modified:2024-10-10T18:29:02Z seems like it would grab only records at that specific time?
This could also be a UI Bug if the data is supposed to return the time, in which case it would be great if you could open that up with Engineering
Hey Geoff! I’ve confirmed that the timestamp is optional in search queries on date-type fields. I’ve also made an update to the docs that should make that a bit clearer. Thank you for helping to improve the docs!