![]() ECStructClass and ECCustomAttributeClass definitions should not have any base classes.Only one base class may have a 'Name' property defined or inherited) Properties must be unique across all base classes (e.g.Additional base classes must be abstract and have the IsMixin custom attribute applied. ![]() Only one base class may be a concrete class (modifier=None).Multiple base classes are only supported on ECEntit圜lasses in EC 3 and additional restrictions are applied.an ECRelationshipClass cannot have an ECEntit圜lass as a base class) A class may only have a base class of the same type (e.g.All 4 class types add a 'modifier' flag which can be None (concrete and not sealed/final), Abstract or Sealed.A consequence of this is that a class may be of only one type in EC 3, where you could make classes which were domain, struct and custom attribute in EC 2. These three types replace the individual 'isDomainClass', 'isStruct' and 'isCustomAttributeClass' attributes respectively. ECClass has been split into 3 discrete sub types, ECEntit圜lass, ECStructClass and ECCustomAttributeClass.The namespacePrefix attribute has been replaced with 'alias'.Schema version now has three digits RR.WW.mm where equal RR indicates read compatibility, equal WW indicates write compatibility, mm is for additive changes or modifications that do not break read or write compatibility.It does not cover all new features of EC 3, rather it focuses on what has changed between the two versions. This page if for people who have used ECObjects in Power Platform and want to learn how it has changed in iTwin.js. Edit this page What's changed between ECObjects 2 supported in Power Platform and ECObjects 3 supported in iTwin.js
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |