La fonction de suggestion automatique permet d'affiner rapidement votre recherche en suggérant des correspondances possibles au fur et à mesure de la frappe.
I have created an integration with our app and have successfully made this work without including a link.
This morning I have attempted to add the link and I'm receiving the response deserialization error which I understand is that the output is not matching the required format/fields.
I'm pretty sure it is to do with the link but I cannot identify the cause. I've checked the usual issues (making sure a link is set or is null etc) but no joy. Any advice?
A # symbol is reserved for a fragment . Any characters that follow a # until the end of the URI are considered part of the fragment and additional # are not allowed. Since the URI provided has more than one # , the one that indicates the fragment should be left as a # and the other one needs to be encoded with %23.
Although, we would generally recommend avoiding the use of # in a URI other than for fragments as it can lead to difficulty in using the URI (due to the encoding requirement) as we are seeing here.
However, the above output displays all entries on the screen and no view more link. Have I overlooked or structured the output incorrectly to enable this feature?
A # symbol is reserved for a fragment . Any characters that follow a # until the end of the URI are considered part of the fragment and additional # are not allowed. Since the URI provided has more than one # , the one that indicates the fragment should be left as a # and the other one needs to be encoded with %23.
Although, we would generally recommend avoiding the use of # in a URI other than for fragments as it can lead to difficulty in using the URI (due to the encoding requirement) as we are seeing here.
This looks to be an unexpected behavior. I would expect it to show 'View all 7 tickets'. In this case, I'll have to check in with my internal team and I'll keep you posted here!
The team has recently pushed an update which appears to have resolved the "Response deserialization error" response for other customers and this may possibly resolved the `allItemLink` not displaying issue.
Can you check if you're still able to reproduce the error now, after the fix was pushed?