[MSI Interface] Parameter values from order parameter messages are not written to variables
Description 
 
In the MSI Interface,
parameter values from "order parameter messages" are not
written to variables as expected. The LOG file refers to: "System.Collections.Generic.KeyNotFoundException:
The specified key was not present in the dictionary". 
This bug has been fixed. Parameter values are written
to variables again as expected. 
To benefit from this
fix: 
 - Update your zenon Software Platform to the latest build of zenon 10
     or higher. 
 
 	Item ID: 280799 
 Version: 14.00 Build: 239777
Version: 12.00 Build: 241649
Version: 10.00 Build: 243056
- Related Articles
- zenon Changesets Excel- Here, you can access a comprehensive list of changes across all maintained versions of the zenon Software Platform as Excel Worksheets. This includes both implemented bug-fixes and new features. Additionally, these lists are available in CSV format ... 
- zenon Changesets CSV- Here, you can access a comprehensive list of changes across all maintained versions of the zenon Software Platform as Excel Worksheets. This includes both implemented bug-fixes and new features. Additionally, these lists are available in as Excel ... 
- Checklist: SAP Interface does not work- Time estimate:  30 minutes Please go through all the points in the following checklist. If necessary, confirm with IT Department any information you cannot verify before contacting your local COPA-DATA Representative. Checklist usage: #. [Quick ... 
- [SAP Interface] Values of export parameters of SAP function are not assigned to variables- Summary Two bugs occur in the SAP Interface: In the Service Engine, zenon variables are not updated correctly. And in the Engineering Studio, import/export parameters are swapped when importing RFC function configurations. These two bugs occur ... 
- [MSI Interface] Wrong TimeStamps in Order Paramter Messages - Description The Order Parameter Messages contained wrong TimeStamps (DateTime.Now - set when the parameter is created) and additionally not all variable related TimeStamps were in UTC format (which supports the required milliseconds). The issue has ...