Appian Community
Site
Search
Sign In/Register
Site
Search
User
DISCUSS
LEARN
SUCCESS
SUPPORT
Documentation
AppMarket
More
Cancel
I'm looking for ...
State
Not Answered
Replies
10 replies
Subscribers
9 subscribers
Views
2826 views
Users
0 members are here
Share
More
Cancel
Related Discussions
Home
»
Discussions
»
Administration
I am importing application and getting error in DS for one of entity. My DS cont
vineeta6579
over 9 years ago
I am importing application and getting error in DS for one of entity. My DS contains total 5 entities.
dataStore _a-0000d97e-24de-8000-927c-010000010000_2288 492 "MMS DS": The import of dataStore [id=492 uuid=_a-0000d97e-24de-8000-927c-010000010000_2288]
could not be finalized: The data store “Test DS” [id=492] was saved but cannot be published:
The data source schema does not match the type mappings: Missing table: ConfigurationStatus (APNX-1-4178-000) (APNX-1-4071-009)...
OriginalPostID-118670
OriginalPostID-118670
Discussion posts and replies are publicly visible
0
Eduardo Fuentes
Appian Employee
over 9 years ago
The relevant error is:
Missing table: ConfigurationStatus
may I know what the question is about this error?
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
vineeta6579
over 9 years ago
Yes, Its showing this error for ConfigurationStatus entity only . But I have total 5 entities present in that DS.
I am wondering why its showing error for this entity only.
I am importing application to new environment and there are no tables existing for this application...
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
Eduardo Fuentes
Appian Employee
over 9 years ago
Simply do a verify of the data store and if you are planning to have Appian creating the tables simply use the Publish button so it creates them for you. If there are other missing tables the Verify will tell you.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
Eduardo Fuentes
Appian Employee
over 9 years ago
Another option to prevent the error is to create the tables beforehand in your RDBMS. You can simply run your DDL scripts (which you can download when the validation fails) in your SQL instance and then do the import.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
Eduardo Fuentes
Appian Employee
over 9 years ago
Note that if the environment has no tables then it's expected that you get an error like this. If you want a clean import log then you better create the tables beforehand either manually of through a DDL
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
Eduardo Fuentes
Appian Employee
over 9 years ago
You should double check what database this environment is pointing to (check your appian-ds.xml) because if it errored out for a single table while you have more entities then most likely you think the database is empty while it's not and it indeed had the other 4 tables already except for this one.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
vineeta6579
over 9 years ago
DB was empty before the application import but it shows error for that particular entity only..
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
Eduardo Fuentes
Appian Employee
over 9 years ago
I confirmed what you're seeing. When tables are missing for more than one entity only one missing table will be reported in the import log, but when you click verify and then "(Download DDL Script)" you will see that it correctly detects that more than one table is missing. So the issue is only with the error message.
The same answer applies, download that DDL and run it beforehand so the import log doesn't show any errors.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
vineeta6579
over 9 years ago
Thanks Eduardo..
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
Eduardo Fuentes
Appian Employee
over 9 years ago
Basically this happens because when the data store is imported it tries to see if the first entity matches an existing table, if it does then it evaluates the second entity and so on, but if one of the entities doesnt match an existing table Appian will error out with that message and save the data store but not publish it and will not continue to see if the rest of the entities match but here's is where the Verify button will explain more through the Download DDL Script button.
If you are going to send this app to someone else and want to avoid this error, download the DDL and have them run it beforehand.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel