We recently upgraded to 2024.1. I had a workflow that would update the "isReadyForMigration" flag using the serverAPI tool. After the upgrade I can't get this to work. I 've tried switching to the /admin/v1/workflows/migratable/{appId} but despite getting a successful run, it's not switching the flag. Can someone help me with what the payload should look like? I've tried so many different things. I can get it to work through the Swagger page but not through desktop. I've tried loading it as an extra column, having the payload blank, having the payload
show as:
'{
"isReadyForMigration": ' + tostring([isReadyForMigration]) + '
}'
and also
'{
true
}'
Solved! Go to Solution.
@lwolfie I wanted to note for anyone else that comes across this post that the nature of this issue (a supported process working before a version upgrade but unexpectedly not after) could indicate a Customer Support case is a good next step, which I believe is in process for this specific situation.
If you run into an issue like this a Community member isn't able to provide insight, you can visit the Alteryx Knowledge Base found here https://community.alteryx.com/t5/Support/ct-p/other-resources, or on Mission Control (linked in the topline navigation of Community) to see if there is a known solution, and if not the process will guide you to open a Support case through the portal.
For anyone looking at this later, the Payload should be:
"true"
Nothing else is needed.
User | Count |
---|---|
3 | |
1 | |
1 | |
1 | |
1 |