Hi @Edwards ,

Not sure whether this is helpful but you might be better off moving on to using ACP’s going forward as it would give you some added benefits such as dependency checks, better versioning and even including them in delivery packages when moving items across environments. It also takes away the need to have App owner credentials in hand.

Cheers

@Sajith D 

Thanks for the response. Fair enough. Are there any limitations / considerations when using ACPs to watch out for? We will essentially be using them with a large amount of modified custom events upon upgrading from IFS 9 to IFS cloud. Are there any size limitations to your knowledge or anything like that for the amounts of items that can be in a configuration package?

If we would go down this route I was hoping to have a configuration package called “Custom events” including all event headers and actions, and just import that ACP. We have about 400 items that would contain between headers and actions.

Thanks,

Lavon

After going through and fixing all of our events, large application configuration packages indeed cause errors when trying to import them. I’ve broken the packages up based on starting letter of the event ID, but the import process still is quite slow and tedious now.
 

Still open to any suggestions that can make migrating large amounts of event changes from one environment to another less painful. Being tied up to import all of the events when we go live isn’t ideal. Has anyone found anything for this?

I suppose I haven’t tried installing the package as a delivery as of yet. I’ll be investigating that next unless anyone has any other ideas