I have some document models for which I encrypt/decrypt some of the fields when the documents are loaded/persisted. For those fields, I also set the annotation indexed=false to prevent the platform saving their bare values in the database.
However, some users have access to those fields and I would like to display them in some Overview model, but the indexed=false part is preventing me to achieve that.
Is there any workaround?
Hello @i.ursu , thanks for your post within A12 discourse! We’ve forwarded your request to our Data Services team. As they are currently very busy, there may be delays in processing. We apologize for this and hope to be able to provide an answer in a timely manner.
Your discourse team
Hi @i.ursu ,
Unfortunately, there is no alternative solution in this case, as the requested approach contradicts the principles of the Query API. Only indexed fields are accessible through the Query API, which is also the default method for supplying data to the Overview section. While it is technically possible to replace the Query API with a custom API for loading data into Overviews, this would require a complete re-implementation of all Query API functionalities. Such an undertaking would be highly complex and time-consuming.
Hello @i.ursu, I am a member of the Discourse team. I can see that there was a new response to your question on Unindexed fields in Overview Models. Do you find it helpful, or should the question remain open?
Thanks ahead for your feedback and have a nice rest of the day!