IIF, CS, CSI FW has pre-requisite to drop already exist table(sample package) and proceed to sample FW media package import; It works well for IIF, CS and we are able to complete post FW upgrade check out with sample data set;
in CSI import, similar drop table statement are exist, but CSI "sample" doesn't auto create tables and not loading dataset. In fact it fails and doesn't allow to move at next level.
We have moved forward with explicit creation of table workaround.
Does any one face this issue? and what work around has been taken?
We would like to make sure no consequence afterward from explicit creation of table and loading CSI sample media.
**Moderation Team has archived post**
This post has been archived for educational purposes. Contents and links will no longer be updated. If you have the same/similar question, please write a new post.
We also faced similar issue during CSI 'sample' import. Out application has CS, IIF and CSI frameworks.
The issue in our case is that, the customer has both the sample tables and the application specific tables in the same schema ( in other words no 'Sample' schema was maintained separately) and during IIF sample import we created the sample schema which caused this issue.
We had overcome this issue by pointing the same schema where sample and application specific tables are there (instead of creating a new sample schema) and performed the CS, IIF and CSI related 'sample' imports, which was successful.
Posted: 6 years ago
Posted: 7 Jan 2016 7:37 EST
Bhushan Patil (BHUSHANPATIL)