Hi @Swarup_Alamuru ,
Good question!
Because the parameter is not always present in each bundle, we need to apply a small trick here.
Firstly,…
Each variable that you map can also be entered in the mustache format. So if you for example past {{newline}} in a mappable field, you’ll notice that it will be transformed into the newline option you can select in the text functions tab.
It’s helpful to give you a bit of context about this, because you’ll need to use it as well. As I mentioned before, you’ll need to determine if a certain parameter exists in the object to build your text structure. So once you have identified these keys, you can reference them. I see your bundle outputs have neat labels, so you should first check what the technical key is by hovering over the name. Then, in your text aggregator, create your IF statement. Reference the right keys to check if they exist by applying the format {{<module number>.<technical key name>}}. So for example: {{29.jobEndAndTicketNotCreatedDate}}. Once added, you’ll notice that the background of that variable is not filled. That’s because it’s not found in the interface of the module you’re linking to.
Also, check this link when your technical key names contain spaces.Closing brackets to insert item –> }} - #2 by Callinetic
I extended the example I previously sent. I added a element newElement in the second JSON parsing module to the first object. Because of my IF statement in the text aggregator, I get the following output now.
blueprint (52).json (18.9 KB)
I hope this makes sense despite being a bit complicated.
Glenn - Callinetic