Skip to main content

Hello we are currently facing major shorcomings when importing ACP’s.

Scenario:

  1. you create a custom field in an entity, this entity is used un a page X
  2. you create a package with the custom field AND the page from your CFG environnement
  3. you import the package in your UAT environnement

Result:

The page X does not show up the custom field on your CFG

 

Reply from IFS: (after 2 months….)

The behavior you are experiencing with Application Configuration Packages is expected and is standard behavior. According to the IFS documentation, when importing ACPs through the IFS Client, some configuration items are ready to use after import, while some require a manual publishing step to be effective. Considering the items included in your attached ACP packages, almost all of them need to be manually published and added to the page as required. You can refer to the following documentation for a clearer idea:

Import Application Configuration Packages: https://docs.ifs.com/techdocs/24r2/040_tailoring/225_configuration/850_configuration_lifecycle_management/025_import_acp/

Publish Package Reference: https://docs.ifs.com/techdocs/24r2/040_tailoring/225_configuration/850_configuration_lifecycle_management/090_acp_references/publishpackage/

 

Problem:

as a customer we have no idea what means “According to the IFS documentation, when importing ACPs through the IFS Client, some configuration items are ready to use after import, while some require a manual publishing step to be effective”

 

Did you encounter similar shortcomings in the ACP process ?

Hello,

When moving from IFS9 to IFS Cloud I deployed numerous things through application configuration packages. I recommend publishing them through the Application Configuration Package page.

 

This way, anything you need published from the package that requires to be published is easily visible and can be published together in one place at the same time.

 

For example, below I have everything required for a custom page I built. A custom entity (or in your case custom fields), a page configuraiton, and a projection configuration. All of these would need to be published in order to be usable in the application. You can go to the specific pages to publish them all one by one (you would need to publish them in the correct order in order to not get failures).

 

Instead you can just come to this form after importing the package. You can see anything that is not published, or if it is published and changes have been made in the ACP, you will see that it isn’t in sync. You can press the “Publish” button at the top of the page, and this will publish anything that isn’t published yet, get it into sync, and do it all in the correct order for you. This saved me significant time in publishing everything during our IFS cloud upgrade, and I find it works quite well as long as everything required is in the package.

 

Thanks,

Lavon

In our case we created a package like you with the Page Configuration, so we tought everything was ok.  But once published and synchronised, the CF were not added  on the page

We needed to manually add them, as explained in the ticket we opened.

Thanks for your feedback

Whats your IFS cloud version? I’m currently using 24R1 but it worked ok back when using 23RX as well.

custom fields should be included in page configurations in ACPs. If you add custom fields and page configurations as above you shouldn’t require to manually re add them to the page again after importing and publishing all the items in the ACP🤔.

For LIST type pages, you may need to add them to the page via the column chooser if the logged in user has column order saved in their profile, but for other page types it should be good to go. 

  • In source environment
    • Create custom field on entity used by page (ensure additional views used on page are also selected in the entity configuration if applicable)
    • publish / synchronize entity
    • add custom fields to ACP
    • Add custom fields to page
    • Save / publish page
    • add page config to ACP
    • Export ACP
  • In target environment
    • Import ACP
    • Go to ACP screen and press publish
    • Custom fields and page config with custom field published

I just tested this between two test environments and it worked well enough

 

Thanks,

LEdwards

We are using 24R2 and 24R2 with SU08
 

Terms & ConditionsCookie settingsAccessibility statement