Validations for moving to the cloud

If your database is already Single Version but you plan to move from an on-premises installation to the cloud, the validation of schema customizations is necessarily stricter. In this case, Infor only allows additive database alterations that can be made through SyteLine forms:

• Changes can be made using the “SQL Tables” set of forms, with the Enforce prefix from AccessAs process default set to 1, and with an AccessAs value specified.
• Changes can be made using the User Extended Tables (UET) forms.

In either of those cases, these types of additive changes are approved:

• Adding tables
• Adding columns (which must be nullable or contain a default constraint) to application tables or your tables
• Creating non-unique indexes
• Creating keys and constraints on your tables
• Adding user defined data types (UDDTs)

If you used the Trigger Management form to generate Insert and Update triggers for user created tables, those triggers are approved. However, outside of Trigger Management, you cannot create triggers, functions, or views in a cloud environment, so those are not approved.

Also, EXTGEN versions of standard stored procedures are approved, but new stored procedures are not approved.

Any alterations that are not additive or that can only be made outside of the SyteLine forms are considered unapproved and cause the validation to fail.

For a current database, the tool validates these areas:

• All SyteLine and third-party schema is present and correct as it exists in the latest Single Version release.
• Custom tables must be prefixed with the AccessAs value.
• Custom columns on SyteLine schema are prefixed with the AccessAs value or were made through the User Extended Tables (UET) forms, and are either nullable or contain a default constraint.
• No additional constraints or unique indexes have been added to SyteLine tables or columns.
• Only extended (EXTGEN) stored procedures are allowed.
• All sites exist within one database.
• All table views have been generated.