If you are performing a search for things and put the constraint as unique ID is in and the is in portion is followed by a list of text, the expected and previously working result would have been a list of all the things that has a unique id that is in the list of texts of unique ids…this is not functioning now, and it only returns 1 result, the thing whose unique id is equal to the first text in the list of text.
Is anybody else experiencing this?
Could you share a screenshot of how your search and your list of texts (ids) is set up? To provide better feedback
it works as expected for me, maybe is something with the expression
@dorilama @Daniel_JTech I’ve set it up 3 different ways to test because my first run on original setup had the issue.
All 3 ways I’ve set it up, get same result, only first item is returned.
it works for me, are you sore the txtx are existing ids? maybe there is a typo
Yes, the ids are stored in the DB, so the search constraint is just taking the text from the DB…the IDs are actually coming from the result of a bulk create via the API, so the IDs do exist in the DB as well.
It should be giving you the full list, here are a couple of suggestions to check:
Check your privacy rules for Quotes and loads objects.
you can also try to use the :format_as_text operator to remove the spaces that could be stored in your database (with :find and replace or :trimmed) and :join or :split_by to manipulate the list or the result, maybe also the :extract with Regex to find the id in the joined list…
Btw, is it normal that you use a constraint with a specific unique id on the “Do a Search for Quotes” operation?
I attempt to approach development with as little issues caused by privacy rules as possible while just building functions/features, so I save them until the end. In this case, privacy rules are not the cause.
This was the issue. I assumed since the first entry was returned, that there would have been no issues with the others, but taking the response from the API call, which is invalid JSON, I had to use a lot of find and replace to get rid of all extra characters…I guess there was a space between the commas.
Thanks @dorilama @Daniel_JTech @guillaume.raballand for pointing out what I overlooked.
This topic was automatically closed after 14 days. New replies are no longer allowed.
