web
You’re offline. This is a read only version of the page.
close
Skip to main content
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Blogs / ELandAX blog / Group Names to be Avoided i...

Group Names to be Avoided in SysOperation Framework Data Contract

Evaldas Profile Picture Evaldas 1,800
Hello AX World,

Data contract is one of the essential parts of SysOperations framework. Based on the groups and data members in the contract a dialog is automatically built. 
Dialog groups are defined by decorating data contract class with SysOperationGroupAttribute




First parameter is the unique name of the group. The name must be unique in the contract and should not be the same as of pre-built dialog controls. A common mistake is to give the name General. Such name already exists and cannot be used. 
Bellow is the structure and names of the pre-built dialog controls that should be avoided:

  • Tab
    • General
      • ParametersToolbar
        • RightButtonGrp
      • ParametersGroup
        • DialogStartGrp
        • MainGrp
    • Destination
      • CurrentPrintDestination
        • DestinationToolbar
          • DestinationButtonGroup
            • Destinations
        • PrinterName
        • PrintDestination
    • Query
      • QueryToolbar
        • RecordsToolbarButtonGroup
      • QueriesGroup
  • ValidTimeRangesTab
    • ValidTimeRangesToolbar
      • RightButtonGrpCopy1
    • ValidTimeRangesParentGroup
  • BottomButtonGrp
    • CommandButton
    • CommandButtonCancel

What about data members? They also have unique names, don't they?
Yes, they do. But the names are not the ones defined in the attribute.


Actual names of the controls have the following structure:

Fld%_1 where % is the number of the data contract member.

E.g. Fld1_1, Fld2_1 ... Fld13_1 ...

BTW, all data members and groups defined in data contract are created under MainGrp group.

Be aware and take care!



This was originally posted here.

Comments

*This post is locked for comments