Data in Decisions

Unknown

Data in Decisions

Unknown

[color=rgb(66, 91, 118)][font=Roboto, Arial, Helvetica, sans-serif]Ive got two questions today! [/font][/color]

[color=rgb(66, 91, 118)][font=Roboto, Arial, Helvetica, sans-serif]When you delete a data structure and go to make one of the same name, we get a warning that the table already exists. Is there a way to prompt Decisions to delete this table so the name can be used again, or do we need to go into the SQL environment and delete it? [/font][/color]

[color=rgb(66, 91, 118)][font=Roboto, Arial, Helvetica, sans-serif]When using Decisions data structures, can you allocate 2 primary keys? (Without making a new column where you merge the two) [/font][/color]

[color=rgb(66, 91, 118)][font=Roboto, Arial, Helvetica, sans-serif]Example: [/font][/color]
[color=rgb(66, 91, 118)][font=Roboto, Arial, Helvetica, sans-serif]Employees table has Company(LLC, RIO, etc) and Employee_Code that make up the unique identifier. In SQL we would use them both as the unique ID (Key) [/font][/color]
[color=rgb(66, 91, 118)][font=Roboto, Arial, Helvetica, sans-serif]​ [/font][/color]
[color=rgb(66, 91, 118)][font=Roboto, Arial, Helvetica, sans-serif]Employee_Code can have the same code for different employees in different Companies. But Employee_Code can not have duplicates in the same Company so the combination makes them unique.[/font][/color]

Unknown

[font=Roboto, Arial, Helvetica, sans-serif]That is one way to get around that validation error. You can also modify the namespace of the new type if you want to preserve any data in the old table. The UI for creating new user-defined types does not have any options for compound primary keys, but if you created the table first and added it as a database table integration, you could select more than one key.[/font]