[Object.UnpackVariables:]
Unpacks the top-level (i.e. not nested) properties of a JObject into variables.
Macro Compatibility
The macro can be used in all input document types and in Report Studio.
Usage
This macro does not display anything in the output document.
Parameter | Type | Presence | Purpose | Options | Default |
---|---|---|---|---|---|
JObject | Mandatory | The input JSON object (JObject). | N/A | N/A | |
String | Optional | Add a comment to make your document template more readable. The comment is discarded in the output document. | N/A | N/A | |
Boolean | Optional | Should NCalc expression evaluation throw error on Overflow |
|
true | |
String | Optional | The text to display should the macro fail to execute. Note that a poorly-specified macro (e.g. omitting mandatory parameters) will still result in an error message. | N/A | N/A | |
String | Optional | The condition that must be true in order for the macro to be executed/evaluated. Must either evaluate to true or false, for example: "3+5=8" or "contains('abcd', 'z'). | N/A | true | |
MacroMode | Optional | The mode in which variables are stored. In the legacy mode (default for Schedules), the variable created is a string and formatted. In the normal mode (default for Report Studio), the output variable is stored as a strongly-typed object, e.g. an Int32 or a List |
|
Legacy | |
ObfuscationType | Optional | Obfuscation type. Use obfuscation to write reports where sensitive data is hidden. When used, ReportMagic guarantees that the same input string will map to the same output string for the whole of the report (but the next time the report runs, it will most likely map to a different value). If you use obfuscation, the property in your macro will not show up and instead, you will see a fake item of the obfuscation type chosen. |
|
None | |
String | Optional | Stores the variable name prefixed by this value. | N/A | N/A | |
String | Optional | If specified, adds a warning message for this macro. This is processed as an NCalc, and the warning message will ALWAYS be present and will be the value of the evaluated NCalc expression. | N/A | N/A |
Examples (3)
Example 1:
This example creates a JSON object (JObject) variable, then uses the [Object.UnpackVariables:] macro store all properties on the object as variables:
[LinearRegression: values=1970-01-01^1000;1971-01-01^2000;1972-01-01^3000, mode=Normal, =>Object] [Object.UnpackVariables: jObject={=Object}]
Example 2:
As the previous example, this example creates a JSONB object (JObject) variable, then uses the [Object.UnpackVariables:] macro store all properties on the object as variables, but in this case it also prefixes the variable names with a specific value:
[LinearRegression: values=1970-01-01^1000;1971-01-01^2000;1972-01-01^3000, mode=Normal, =>Object] [Object.UnpackVariables: jObject={=Object}, variableNamePrefix=Kryptonite_]
Example 3:
This example takes in a JSON object (JObject), then creates 4 JArray variables named: BackgroundTraffic, BestEffortTraffic, VideoTraffic, and VoiceTraffic:
[Object.UnpackVariables: jObject=`{"BackgroundTraffic": [1,2,3,4,5,6,7,8,9,10,11,12,13],"BestEffortTraffic": [14,15,16,17,18,19,20,21,22,23,24,25,16], "VideoTraffic": [10,20,30,40,50,60,70,80,90,100,110,120,130],"VoiceTraffic": [0,0,0,0,0,0,0,0,0,0,0,0,0]}`]