Hi, When we promote our application from one environment to another,

senthilar over 10 years ago

Hi,

When we promote our application from one environment to another, the Data Store gets created successfully. But the Data Source is not set automatically, though the data source name is same across environments. This also caused the following error message during import:

Problems (1):
dataStore _a-0000d8bc-879d-8000-effe-010000010000_2257 218 "Sales_DataStore": The import of dataStore [id=218 uuid=_a-0000d8ab-879c-8000-affe-010000010000_2257] could not be finalized: The data store “Sales_DataStore” [id=218] was saved but cannot be published: The data source schema does not match the type mappings: Missing table: salescustomerinfo (APNX-1-4178-000) (APNX-1-4071-009)

We had to then manually set the Data Source for the DataStore by choosing from the dropdown.

Is this an issue? How can this be prevented?...

Discussion posts and replies are publicly visible

Parents

0 Eduardo Fuentes
Appian Employee
over 10 years ago

Then your observation #2 and #3 is the relevant one. By design Appian cannot deliberately create tables in a target environment, it would be too risky to allow to do this by a simple import. Appian imports and saves the data store in draft mode so you, as the owner of the environment, can validate whether the table should be created or not.

Imagine what would happen if there's a typo or misconfiguration in the XSD and Appian ends up updating your table or creating it with that typo. With this mechanism the person doing the import is alerted so he can check whether it can simply instruct Appian to create the tables in this environment too or if there's something to fix in the XSD to match to the existing table.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Reply

0 Eduardo Fuentes
Appian Employee
over 10 years ago

Then your observation #2 and #3 is the relevant one. By design Appian cannot deliberately create tables in a target environment, it would be too risky to allow to do this by a simple import. Appian imports and saves the data store in draft mode so you, as the owner of the environment, can validate whether the table should be created or not.

Imagine what would happen if there's a typo or misconfiguration in the XSD and Appian ends up updating your table or creating it with that typo. With this mechanism the person doing the import is alerted so he can check whether it can simply instruct Appian to create the tables in this environment too or if there's something to fix in the XSD to match to the existing table.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Children

No Data