We have noticed that when the 'Hide parameter' option is used, we can no longer retrieve the value of that parameter from Automation scripts. In our case, we used the element.GetParameterByPrimaryKey method. This means that when users change the information template it has an impact on the automated actions and might lead to a long investigation to figure out if it was caused by an information template.
Is this expected that the information template has such an impact or is this a bug?
An information template can have an impact on your Automation script , especially if you refer to parameters using their names. If you rename a parameter, then you will have to use the new name to get or set that parameter.
If you want to be independent from the information template, then I'd suggest to manipulate parameters using PID.
No, this is not what I’m saying. If you want robust automation scripts, then you need to refer to parameters using PID instead of names.
We were using the GetParameterIndexByKey with the PID, but it started to fail after the column was hidden.
Michiel, if you use the GetParameter method, then you’ll get a value even if the parameter is hidden. One of the overloaded method allows you to get values from a table.
Will that be enough to fix the issue in your automation script ?
If you see that there are issues with other methods, please open a ticket so that we can further investigate
Thanks for your feedback Emmanuel. This would mean that Information templates should never be used when you are running automated actions from automation scripts.