Why are validations from EDM to Cloud GL not the same as within the Cloud GL interface?

Summary:

We are seeing that enforced validations from EDMCS are not the same as validations being enforced when manually updated the COA segments in the Could GL interface.

Content (required):

An example is the validation for the Summary property. In Cloud GL, you can have the summary property set to TRUE for an member in the GL segment, but in EDM, to have it set to TRUE, it must be in a hierarchy set with children under it.

Version (include the version you are using, if applicable):

Code Snippet (add any code snippets that support your topic, if applicable):