I want to use a queryRecordType in a portal interface and obtain the data, but I need to filter the data so as not to recover everything. What should I do to be able to filter the data since it does not allow me to use a queryFilter in the portla interface? I get this message: "Service Account", I have the Service Account user configured as administrator in the record in case it could be due to permissions
Discussion posts and replies are publicly visible
enriquec149
IGNORE WARNING IT WILL WORK IN PORTAL AS IS. Test and verify in portal and interface it will work as expected.We know this unexpected behaviour, You can use queryFilter in portals to retrieve filter data.If you are still looking for better approach go through below mentioned steps.
If your goal is to pre-filter data using specific criteria before it's even retrieved with a!queryRecord, you'll need to use the Process Model Filtering approach.Trigger a process model execution from a button or link within your portal.The process model itself can handle data retrieval and filtering using a!queryRecordType with a!queryFilterSave the filtered data in process variable and pass to interface.Let me know if that works for you
When i try it in my CE site in a live portal, I do get the same warning message in my interface when I add a hardcoded queryFilter, however it does actually work when viewing the portal. I'm not really clear what the mis-match is. I would perhaps guess it's to do with a!queryFilter() traditionally being associated with QueryEntity instead of QueryRecordType, though that's just a guess.
I know that's strange behaviour.queryFilter() can be used with Portals if it is connected using an integration and web API.
I assume when they updated portals to allow for a!queryRecordType() to work at all (since it didn't originally), they forgot to update the warning mechanisms to also allow a!queryFilter. I also get the warning message in your screenshot, but also, it still works for me in my live portal - and I'm under no illusion that they'll be going backwards with this functionality in iterative updates, so I wouldn't be too worried about using it for now in spite of the false warning message(s).
This is exactly what happened. Sorry for the red herring! You can use queryFilter in portals just fine. The warning will be removed in the 24.2 release.
Keanu Delgado said:This is exactly what happened.
excellent, thanks for confirming!
Thanks enriquec149 for quick update.