We have encounterd an issue where The package has been successfully installed in another environment; however, certain modifications fail to reflect. Upon examination of the installation log, the message "Actions skipped for schema" is encountered for specific schemas. Could someone assist in resolving these errors?
Ensure these schemas are not unlocked in the target application to which the package is installed. Otherwise we will need the complete installation log and the package itself and access to the app to which the package is installed to review why these information messages pop up.
Is there any easy way to transfer changes from section Pages the (Full User) to Portal Pages. I have created three pages as a Full User, and i want to transfer these modifications to Portal also. I want to create the same pages in Portal. Is there an easy way to do this automatically ?
Or i would have to repeat dhe same process to Portal by hand ?
That shouldn't cause any problems as the Application Form Edit Page that you are setting as the parent inherits it's properties from the base section page.
In order to achieve this you can go to the Advanced settings and find the page that you would like to transfer, the data type will be "Client module". Then you can copy all the content that is inside of the "Diff" array of objects and paste it into the page that you have in the portal. If there are any business rules or other differences you should copy them as well. In the portal page you should leave as it is the entitySchemaName and the details of the page, the rest should look as it looks in the page that you are transfering.
That shouldn't cause any problems as the Application Form Edit Page that you are setting as the parent inherits it's properties from the base section page.
We recommend to transfer packages between environments deployed on the same version of Creatio in order to avoid unexpected issues after or during the process.
You can follow this update guide where updating process is described:
You can use system functionality "Bind data" for such purposes. You need to choose the package you want to export. Click on "Data" tab in the configuration and add a new data file. There you choose "Translation" object and columns, data from which should be exported. You can also click on "Display data" button on the right part of the data binding modal window, so to see which exactly data will be added.
Afterwards, as yoo export and install package on other instance, the data will be installed along with the package and the translation object will be filled with new translation in database.
If you decide to update existing data, please set "Force update" tick in the left part of data binding modal window, where all settings are.
Any idea how to fix this issue, we have already changed the title of our section and disable the add record mini page in our development but when we transfer our package (using export to archive and install application using install application) to Production, still the add record mini page is enabled and the title does not changed at all.
The the reason for this issue might be in not compiled production system before transferring packages. Please, compile the production system and update the database structure before the package installation. Once the packages are installed in the production environment try to compile and update the database structure again. This should resolve the issue.However if it still persists - please contact our support team via email support@bpmonline.com to have a closer look into your particular installation.
