- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-20-2023 02:01 AM
Hello,
i have such Scheduled Script that sends in an email a personalized link to managers of some groups. As in the filters there is a condition "is one of" and there are a lot of groups the link is really long. Once sent and opened it gets converted to sysparm_tiny. The issue with this is that for short link the GROUP BY assignment group is working but once link is converted it doesnt. I tried to change the sys property that deactivates the conversion to sysparm_tiny, but GROUP BY was still not working. I also changed the max characters in a URL from default 1024 to more, but it didn't help. Does anyone have advice why GROUP BY is no more working once i send so long URL ? For URL without the condition is one of (exact condition: Assignment_group.name "is one of" Many different groups) it is working fine.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-20-2023 02:06 AM
Hi @lukasz szumilas ,
It's possible that the length of the URL is causing the server to truncate the request, which could be causing the GROUP BY to fail. One option to consider is to break up the request into smaller chunks that can be handled by the server. One way to do this is to use pagination, where you only request a certain number of records at a time and then request the next set of records when needed.
Another option is to use a POST request instead of a GET request. With a POST request, the data is sent in the body of the request rather than in the URL, so you can send larger amounts of data without worrying about URL length limitations.
You may also want to consider optimizing the query to reduce the number of records returned. If you can narrow down the search criteria to only include the relevant records, it may be easier for the server to handle the request and for the GROUP BY to work properly.
Thanks,
Ratnakar
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-20-2023 02:06 AM
Hi @lukasz szumilas ,
It's possible that the length of the URL is causing the server to truncate the request, which could be causing the GROUP BY to fail. One option to consider is to break up the request into smaller chunks that can be handled by the server. One way to do this is to use pagination, where you only request a certain number of records at a time and then request the next set of records when needed.
Another option is to use a POST request instead of a GET request. With a POST request, the data is sent in the body of the request rather than in the URL, so you can send larger amounts of data without worrying about URL length limitations.
You may also want to consider optimizing the query to reduce the number of records returned. If you can narrow down the search criteria to only include the relevant records, it may be easier for the server to handle the request and for the GROUP BY to work properly.
Thanks,
Ratnakar