This site uses different types of cookies, including analytics and functional cookies (its own and from other sites). To change your cookie settings or find out more, click here. If you continue browsing our website, you accept these cookies.
09-10-2020 09:18 AM - edited 07-30-2021 11:35 AM
Notes
The the last two lines of that article look to be incorrect, I think that they should read:
Schedules without workflow schedule name by mongo id
Schedules with workflow schedule name
The article fails to mention that the schedules list is sorted by Schedule name even when the sort option on the Workflow name column is chosen?
The screen capture in the article even shows that the person choose to sort by Workflow and not by Schedule but that isn’t called out.
In the UI, if the Schedule does not have a name, then the Workflow name is shown (repeated) in the Schedule column. Because of this the only way to identify the where the Schedule name is missing is to notice that the rows are not correctly sorted.
Looking at the creation dates of the Schedules on our system that I have had to fix it would appear that earlier versions of the Gallery automatically copied the Workflow name into the Schedule name if the latter was not specified. I'm not sure why this was changed as it seems to be a sensible solution to the issues that have resulted from the changes in this version?
@JohnPelletier could you help me out with @DanielG question?
Any updates @JohnPelletier?
@jayj1000 I just tested this in 2022.1 and still see schedules without an optional schedule name being sorted first and then schedules with an optional schedule name being sorted below that. See below image for what I tested. I will look into the initial submission and see what the status is.
@jayj1000 After looking at the issue and internal notes it looks as though the best route to go is to use the v3 endpoints in 2021.4 and above to modify the schedules to have an optional schedule name OR have all schedules not have an optional name.
You can utilize the v3 macro pack created by our solution architecture team to do this with an Alteryx workflow:
I have updated the issue notes internally and apologize for the inconvenience but hope the workaround helps.
@JamesHa Thank you for the link explaining the v3 macro. We are currently using 2021.3 and the schedules are not being sorted by schedule name or workflow name as you have pictured in your previous comment. They are being sorted via a randomly assigned mongo id as explained at the top of this thread. Was this problem corrected at version 2022.1 or a different version?
@jayj1000
The sorting behavior has not been changed and no changes are imminent. Starting with version 2021.4 the v3 endpoints are available to use as suggested in the link JamesHa provided.
"and no changes are imminent"
This is disappointing to me. We are talking about having a standard web UI element - a table - sort in a user intuitive way, or at least not to mask/conflate the problem by copying data into null fields only at display time (current functionality) and not when a record is created (old functionality).
In addition the table sorting by Schedule name even when the sort option on the Workflow name column is chosen is surely just a flat out bug?
@Paul_Holden I agree. This is a very basic feature that should be available. We have over a thousand schedules on our team and it's nearly impossible to find any specific one. Please add a more reliable sorting method by default, or add a search bar for schedules @JamesHa @LisaL.
@jayj1000 @Paul_Holden I understand your side of it and will do my best to ensure that your concern is heard and accounted for. As I do not work with the development team here is the best that I can do for you:
Hope this works for you and the link to the drop location will expire 12/31/2022
@JamesHa support case opened. Thank you.