We seem to be running into an issue
We seem to be running into an issue where TS occasionally fails to respect filter parameters in
metadata/search - it's returning many more results than what would be expected (we are filtering on favorites for a given user). The problematic request/response is the second one in the HAR file.11 Replies
Hi @Leslie Chiang - Can you please send the HAR file through email to me and @shikharTS and delete the HAR file from the post.
@shikharTS can then help you out with this
Shared the details in the DM @Leslie Chiang
I am trying this out internally. I think there is a bug here. Give me sometime to fix this. Can you raise a TS ticket for this?
Sure, thanks for looking into it! Can you remind me where to go to raise the ticket?
Opened case 00376733
Hi @Leslie Chiang, I am raising a fix for this, meanwhile can you check if giving the userGUID, in the filtering for favourite options, instead of the username works for you or not. Giving the GUID directly works for me, but there is a bug with giving the username and I am raising a fix for that. Can you check using userGUID works for you?
Thank you for your work on this. Right now we don't have access to the userGUID in our frontend so I am unable to check this. Once we move this to a backend request we would be able to send userGUID
If possible you can check on the playground in TS. Given the username, you can search for the user using API. You will get the userGUID from there. Then call the same API using userGUID instead of username. If you can't check can you confirm one thing for me, does that user for which you are getting the error, belong to all orgs?
Sorry for the delay - I was trying out some other changes in conjunction - switched to TrustedAuthCookieless and tokenizedFetch and the results were consistently wrong there - with both tsUsername and userGUID. Overall we would like to switch to the Cookieless approach as we've been running into a lot of issues in multiple tabs and instances with the Cookie approach. Do you need me to send sample HAR files for the issues there? or would the trace ids do?
I see, can you create a support case for these issues and attach the relevant files? And we will help you there..
What is the error there? Are just the results wrong?
Okay, I'll open a support case for these as well - the results are wrong/mix of right and wrong, but consistently so.
Can you give me the curl command for which you are getting wrong results, I can try to repro on my end
Just sent via DM