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

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?...

OriginalPostID-104327

OriginalPostID-104327

  Discussion posts and replies are publicly visible

Parents
  • This is the relevant message: "The data source schema does not match the type mappings: Missing table: salescustomerinfo" this means that the target environment doesn't have a table called salescustomerinfo, therefore it's required that you do a validate of the data store so you can instruct Appian whether you want it to create the table automatically or if you are going to create it on your own.

    Another possibility is if the name of the data source (NOT data STORE but SOURCE) is not the same on both environments, in this case the message will be different and there's a need to map to the corresponding data source in the target environment after importing.
Reply
  • This is the relevant message: "The data source schema does not match the type mappings: Missing table: salescustomerinfo" this means that the target environment doesn't have a table called salescustomerinfo, therefore it's required that you do a validate of the data store so you can instruct Appian whether you want it to create the table automatically or if you are going to create it on your own.

    Another possibility is if the name of the data source (NOT data STORE but SOURCE) is not the same on both environments, in this case the message will be different and there's a need to map to the corresponding data source in the target environment after importing.
Children
No Data