Ingesting JSON object into data action instead of creating string collections in a template

Now that there are some rudimentary blocks that can be used to parse JSON formatted data directly in Architect - is there a method for returning the result from a data action as a JSON object?

The use case here is - we have data returning from an API that we would prefer to ingest in a secure flow. (Why are there not Secure Common Flows is beyond me- as routing in and out and returning the same place in a main flow is forcing a form of spaghetti code within Architect flows. )

From what I can see - although the documentation around the new JSON blocks and secure data blocks doesn't seem to exist (or at least I can't find it) Data can persist through the call flow as an encrypted JSON object (but does it persist from a secure flow to a normal flow) ..

So it seemingly would be possible to encrypt data when the data action takes it in, and then have it persist with the call so it can be used later in the call flow....

Even if the new Secured data blocks aren't the right thing - keeping the data in JSON would be great -

We have data coming through that has elements with sub elements that we want to keep the association with (So possible to have multiple accounts against one customer etc)... As it stands it looks like the best way to handlethe data I need to process - is to translate the data coming into architect as collections and put them back into JSON objects ..... So clearly - if we were able to simply pass the JSON return object from the data action to a JSON object in Architect that would save considerable time.

Or am I just completely off what is going on here (Documentation links if they exist please!!!)

Hey Allan,

I can see how having additional tooling in place to simplify passing JSON to and from architect would be really helpful. Please open up an idea on https://genesyscloud.ideas.aha.io/ for this and provide a link to it in this thread.

In the short term it is possible to perform JSON escaping and unescaping inside of data actions via string replacement, however it is messy. For example, I posted a way to unescape JSON in a data action here: Microsoft Dynamics data action problem - #3 by scm_pa

I recommend opening a parallel thread in the architect room about how Secure flows / data work, as I don't have any insight or control over how it works.

--Jason

Yeah - I'm doing some similar stuff, I'm pretty sure it was an earlier answer you gave to someone. - but I'm finding my templates are getting more and more complex ..

I'll definitely put in an IDEA for this one.

Thank you, having ideas up for new features really helps us identify widely useful features!

--Jason

+1 for not having to flatten json data between Data Actions and Architect Flows. If you submit an idea, link it here and I'll certainly vote for it.

This topic was automatically closed 31 days after the last reply. New replies are no longer allowed.