CRM and SQL Smart Object Export | Import

The CRM and SQL Export | Import SmartObject Import feature enables users to import SmartObject definitions which were created from a similar K2 for SharePoint source. The feature is especially useful when moving processes and their respective dependencies i.e. SmartObjects, between environments. A common example of this would be moving SmartObjects from a development environment across to a similar production environment where the SmartObjects would need to persist as a dependency. The feature can also be used to synchronize existing deployed SmartObjects with a new definition template.

During the process development cycle, K2 SharePoint SmartObjects are created using a SQL Server’s Databases or CRM Servers Entities. These items, exposed as SmartObjects are used in the development of processes within a development environment. When the SmartObjects are migrated, the SQL or CRM Export feature acts as the export vehicle to move the SmartObject definitions from the existing server to the new server.

When performing the export, for SQL the databases must be exported with the *.XML file as well

Why use this feature?

When a SmartObject is created for example in the , a GUID is assigned to the SmartObject; this is used to uniquely identify the SmartObject. If another SmartObject is created in an adjacent environment with the same name, the GUID will not be the same. Processes deployed from a development environment to the production environment will not be able to locate the SmartObjects that they need even if the names are the same, the GUIDs are not.

The export SmartObject feature ensures that when the SmartObject definition is imported into the target environment, the definition will be used to recreate the definition as exact copies. The deployed processes will be able to identify them owing to the duplicated GUID and proceed as per normal.