GUID and It's Association with Database Structures

Unknown

GUID and It's Association with Database Structures

Unknown

Does Decisions create an associated GUID for each record?

What is it associated with in the case of a Database Structure?

[font=Roboto, Arial, Helvetica, sans-serif]What is the intended way to promote a User Defined - Database Structure’s records from one environment to the next (i.e - DEV/UAT to PROD) Are there actual entities that live in a Decisions Repository project? Or Does a database deployment script need to be used to promote the contents of the Database Structure to subsequent environments?[/font]

Unknown

[b]Does Decisions create an associated GUID for each record?[/b]
Yes

[b]What is it associated with in the case of a Database Structure?[/b]
With Simple Database Structures, they get a GUID generated automatically as well. You can substitute the GUID with an ID of your choosing, but you run into the risk of conflicting IDs if you are using a mixed process for generating the IDs.

[b]What is the intended way to promote a User Defined - Database Structure’s records from one environment to the next (i.e - DEV/UAT to PROD) Are there actual entities that live in a Decisions Repository project? Or Does a database deployment script need to be used to promote the contents of the Database Structure to subsequent environments?[/b]
Data from User-Defined Database Structures are not transferred when you export project. You have a couple of options for migrating the data in the table. The first is, as you suggested, by writing a script to copy/move the data into the production database. The second option would be to use the [b]Export Data To CSV[/b] option on the data structure. You could then import that data using the same option on production.