My goal: to Develop this workflow with an actual example of the JSON that will be passed to the workflow
Issue: I have a working workflow whose test JSON just appears as the startTrigger.data, in the new workflow I am working on, it is in a node "_retool_exampleInputJSON" which would be fine if it was uniform and I could program for it, but I don't want to publish this to prod just to have it not work because the parameter looks different.
Steps I've taken to troubleshoot: I have tried using the exact same JSON loadout as the currently working workflow to test.
Additional info: (Cloud or Self-hosted, Screenshots) self-hosted
working workflow:
Hi @Shegs, thanks for reaching out! If I am understanding your issue correctly, you want to have an uniform way to access your data and its properties?
One thing I would try in your example workflows is to standardize the same block following the start trigger block. For example, both can connect to a code block or both can connect to a query block. You can also standardize the Javascript code running in both blocks to either be JSON.stringify or referencing startTrigger.data directly.
If you are going to have another block after your current workflow, you should be able to reference your data object's properties as < previous block >.data.< property name >
Let me know if these steps don't work as expected for your workflow.
Workflow A will be the workflow I just finished last week and is currently running in production. the screenshots for which I will take from our Development Environment.
Workflow B will be the workflow currently under development that I started working on a few days ago.
Currently if I open Workflow A and look at that Javascript code to stringify the JSON from the Test JSON Parameters field, I can do so just by referencing startTrigger.data. this is how I would expect Workflow B to also work.
Workflow B for some reason, wraps the JSON inside the Test JSON Parameters field inside of another JSON object labeled: _retool_exampleInputJSON
this is the issue I'm having. I have no idea why this new one is having an issue but my old one isn't.
Where am I going wrong that even a brand new workflow as of a minute ago is also causing this issue, but one I created last week is fine?
That's very odd, @Shegs. Were both workflows initially created on version 3.196.3? I've tried replicating this in a few different ways without any luck. Would you mind sending me a JSON export of Workflow B? Or any newly created workflow, I guess, as you mention that it keeps happening.
Sent.
and no, the Workflow A was created before the update to 3.196.3
but I would assume that they would act similar after the update since I'm trying to do the same thing.
Hey @Shegs - I talked to the team and this bug was fixed not too long after the release of 3.196.0, so you might have just missed it. Your best option at this point is to upgrade to the most recent stable release - currently 3.196.5.
Note that this fix is not retroactive, meaning you will need to recreate any affected workflows. Let me know if you have any questions!
Were both workflows initially created on version