We'd love to see some other attempts at this as the solution we built, eh, it works but I know there are other ways to approach this. Roll up yer sleeves and give it your best shot.
The Problem
We have a Data Table and a Request Table and they are related by the Request #. Business users are able to populate a UI with requests to update certain fields with specific formulas. The data that this will be applied to is loaded in the Data Table w/ the autogenerated request number, while at the same time the Request table populates with the auto populated request number, the field that will be impacted and the expression to be applied which is loaded in JSON. (This above process is fixed and is not changing) Assume the expression data has been cleansed and parsed into the presented state.
Problem: Be able to take the expression from a field in one table then apply it to a separate table data set.
We tried a number of options to attack this and kept being stymied by translating [expression] field to use the actual listed expression and not just show "[SALES_TOT] +10" displayed in the column. A possible solution was stumbled upon with the Dynamic Formula Crew Macro - but even this felt "off label" in its set up and use.
Good luck
@No-Sass
I am sorry but can we just combine these two data steam then seperata later again?
Yeah, totally. Purposefully kept the data streams as close to the beginning as possible.
Hey @No-Sass
Here is another way of doing this. Since you already have expressions and field names coming from other data source, you can use dynamic replace tool to execute those expressions on primary data.
To add here that the field to show the new updated value is the "UPDATED VALUE" field, essentially showing both the old value and the new value on the same line.
While that works for the first solution, when the expressions include field references, it does not...
@No-Sass In case of multiple expressions on same record are applicable, what value do you need in updated field ?
While the expression may be an If statement (IF [SALES_TOT] > [STORE_TOT] THEN [STORE_TOT] ELSE [SALES_TOT]+155) or some other expression of varying lengths, there will always and only one expression per request
It is my understanding by request we are referring to one single record in data. I have done modification in workflow to update expression output in updated_field instead of original column. PFA for reference.