Hey, there are two possible solutions that I can think of off the top of my head:

1. Create the field manually using code in the desired package and later delete the schemas from the Custom package. (This is less recommended).

2. Create a 3rd package, let's call it Y package, navigate to the dependencies of the X package and add a dependency to the Y package, move the files from the Custom package to Y package.

This should solve the issue for you as the field will be available in the Y package, and because X depends on it, it'll also be available there and thus it should work.

I hope this helps!

Edo Sagron,

thanks, will try!

Hi Altaf Hussian,



If it’s a regular package you can use the Newtonsoft.Json core library, but for the assembly package, the required DLL must be added to the package explicitly.



The Assembly package is like an external cs project.

If you want to use an external library like Newtonsoft.Json.dll in your project - you have to specify it as a reference for your project (using) by adding that dll to the package.



The same can be achieved by using the Terrasoft core class without adding any explicit dll reference into the package as below,

Example of the code:

using CommonJson = Terrasoft.Common.Json;
string orderItemsInput = CommonJson.Json.Serialize("YourObject");

string orderItemsInput = Terrasoft.Common.Json.Json.Serialize("yourObject");

Terrasoft.Common.Json

Serialize Polymorphism

 

BR,

Bhoobalan Palanivelu.

Hello Sasori,

In order to deactive the filter based on employee it is just needed to click on the cross sign, and you will see all the accounts.

Alternatively you can create a replacing view model for the schema PlanningAccountDetailV2 and modify the method getFilters according to your needs.

 define("PlanningAccountDetailV2", [],

    function() {

        return {

            entitySchemaName: "Account",

            attributes: {},

            methods: {

                getFilters: function() {

                     this.callParent(arguments);

                    var filters = this.sandbox.publish("GetSectionFilters");

                    if (!this.Ext.isEmpty(filters.filtersValue)) {

                        this.setFilter(filters.key, filters.filtersValue);

                    }

                }},

            diff: /**SCHEMA_DIFF*/[]/**SCHEMA_DIFF*/

        };

    }

);

As for the section wizard, this whole detail was created with code, so it would be not possible to enable it. But the first option by clicking the cross sign would be the more simple one.

Best regards,

Dariy

 

Thank you very much Dariy.

Hello,

The reason could be that the 'IsChanged' attribute of the scheme in the needed package is set to 'true' when it should be 'false'.

Hello Mariam,

According to the application logic, the changes in the access rights always generate the replacing object in the Custom package, regardless the one you have in the Current package.

We are aware of that and working hard to fix that in our future releases. 

Hello Kyrylo,

Thank you for your response,

In this case, how to proceed in order to add changes to my package for transfer between environments?

Thanks,

mariam moufaddal,

if you switch on Access rights in your package in configurator, these changes will be transfered with your package

Kind regards,

Vladimir

Hello,

Please refer to this Academy article (+ this) to define the package dependencies.

Best regards,

Mira

hi @Jonathan,



It's recommended to have the package that has access/connected to all the base packages of the Creatio bundle. Also, the package dependency diagram in the configuration section will give insight into the structure of the package of products (Sales, Service, Marketing, Studio).







In your case (i.e., sales bundle), the package SalesEntepriseSoftKey_ENU shall be added in dependency. Please be informed that SalesEntepriseSoftKey_Obselete package shouldn't be added in dependency as this might be removed in the product updates.





BR,

Bhoobalan Palanivelu.

Bhoobalan Palanivelu,

Hi @Bhoobalan,

The problem here is that if I put the dependency on "SalesEnterpriseSoftkey_ENU" package, it will only work with the "SalesEnterprise" products of Creatio, not SalesTeam nor SalesCommerce.

Best regards,

Jonathan

Hello Petrika,

Parameter IsLocked mainly affects if you can edit the schema or the package.  Only the author of the lock can edit these elements. In the database, this author isn't mentioned and you can see only IsLocked.

The system will check the author on the other level.

I believe the error is indicating that you have bound data in your package for SysModuleInWorkplace and the bound data references a record in SysWorkplace that doesn't exist in your package. 

Basically, you've added something to a workplace and bound that in the package. However, The workplace itself hasn't been added as bound data to the package.

To solve this, add bound data for the SysWorkplace record that is referenced by the SysModuleInWorkplace record currently bound in the package.

Ryan

Hello

Please follow the described steps on how to bind data:
(Use your ID from error message)
1. Create a "Data" element in your package. Example in screenshot below.

2. Select the SysWorkplace object. Example in screenshot below.

3. On the "Bound Data" tab, add the id specified in the error. Example in screenshot below.

4. Select the id specified in the error from the list. Example in screenshot below.

5. The result.

 

Dear Petrika,

Unfortunately, we do not have any scenarios and instructions for such cases.

We strongly do not recommend installing packages to lower versions of Creatio.

The only 100% safe and correct way is developing functionality for the specific version of Creatio.

Best regards, Alex.

Aleksei Efimenko,

Thank you Alex!

Dear Gareth, 



The logic behind this behavior is that when any changes comes in the package they should not be directly changed since packages can be distributed by third-party publishers. 

Only way to change functionality installed is to re-define the code or add new methods within the new replacing module in your custom packages. 



Kind regards,

Roman