API - ISoMappingRule and ISoMappingRuleCollection are located in the wrong namespace
Description
Concerning Edge API the ISoMappingRule and ISoMappingRuleCollection
classes were located in the Scada.AddIn.Contracts
namespace. This was not correct.
Therefore, these classes have now been moved to the
namespace Scada.AddIn.Contracts.SmartObject for
zenon versions 11 and higher.
To benefit from this fix:
- Update your zenon Software Platform to the latest build of zenon 11 or
higher.
Item ID: 264005
Version: 11.00 Build: 157700
Related Articles
IIoT Services API delivers the wrong report parameter data type, equipment tree nesting or time filter granularity when the report parameter name contains an underscore
Description In the Report Engine, a parameter name with an underscore is used in a report. If this report is deployed with the "Available in IIoT Services" option active, the IIoT Services API returns the wrong report parameter data type, the wrong ...
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 ...
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 ...
API Error when running Instance Wizard (GSK)
Description If a Smart Object instance is created with the Instant Wizard (GFK) and removed again with this wizard, an API error occurs when another instance is created. The error message refers to: "Attempt to read or write protected memory." This ...
LOGIC: StratonNG driver generates a wrong external timestamp after conversion from v12 to v14
Description If a zenon Logic project has been converted from zenon version 12 to zenon version 14, the external timestamp of a variables set by VSI* functions went wrong (e.g. vsiCopy). The issue has been addressed and the VSI* function handling of ...