Hi Wasana,

Provisioning  environments in the BP, consider only what we have version controlled in GIT.

How did you handle custom fields? Are they in GIT or directly uploaded?

But again even you version Custom fields, it will not publish automatically upon provisioning.

If you refer a configuration(custom field, view, LU, etc. ) in some other place, it should be installed and published in the database prior to its use.

In legacy systems prior to IFS Cloud, We created a script to make it even publish to avoid such issues. You may need to modify the deploy.ini to set the correct order of deployment as well.

Best Regards,

Chamila

Hi Chamila,

Thank you for the information.

Yes custom field is git controlled and it is imported after IAL is the issue.

As i understood from your comments there is no way to change the configuration import and ial deployment order in deploy.ini , may be install.tem .

This means we have to send the configurations to CFG first  via delivery and then IAL?

/Wasana

This means we have to send the configurations to CFG first  via delivery and then IAL?

Yes, this is best way to handle it.

If you need to send both at the same time through the automation, you need to write two scripts for custom field(publish first) and  IAL(may be as ins) and list them in the deploy.ini. In IFS Cloud, we cannot change the install.tem.

But I prefer to do directly in the use place without having them GIT. But R&D suggestion is to version control all the configs as well. I think we need a discussion here for that.

.

Thank you Chamila. I agree. if we git controlled configurations there should be a proper order with installation. 

I highly suggest to create from the configuration a customization and have that field in the CBP git repo too. Never create references like (even when it works and its easy)

CF Field → IAL

IAL → CF Field
 

P.S. IAL are deprecated, the view should be created in CBP/ git anyway :)

Hi JohannesKnust,

Thank you for the information,  Good point to make configuration as a customization and then use IAL.

in our case, this is an uplift to cloud and old system is using this IAL  , so  we need to keep IAL though its depreciated. 

/Wasana

I am having issues with deploying the IAL too. Seems like I get an error that the Tablespace does not exist but when I check it does exist. Any ideas on why else that could be?

is the IAL USER(Ifsinfo) is set up? and &AO.. prefix used for view and API calls?

i think this is set up from what I can see. Not sure how to check if IAL USER is set up.