Skip to main content

Using EDI specifications

You should use these definitions by inheritance from them (creating a structure that customizes another structure using the new structure wizard in your own project), even if you don't intend to actually customize the transaction set. The main reason for this is to allow flexibility for a migration to a later version. To migrate to the later version you would need to change only one place which is where your custom structure inherits from the standard structures defined in the specification project. Another reason for this is these specification definitions are immutable in a read-only project, so you won't be able to associate your own sample documents directly with the structures in this project.

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – let us know how we can improve!