Hi Perrika,



You can find all the necessary information in the corresponding article here and here.



Best regards,

Bogdan

 

JUAN PABLO OSUNA DE LEON,

Hello,

In most cases the package is being transferred from dev site where it was developed to prod site where no development should be done, therefore once the package is installed to the target site (prod site in this example) it's locked, as no further development should be done directly on the prod site, and if you need to apply changes to the package, you should do so on dev site and transfer changes with the package once again. One more thing to mention, if you are about to install the package once again to the target site where such a package already exists, it should be locked on the target site for customizations to be applied properly.

According to the logic mentioned above, after installing the package transferred from dev site is locked on your on-site instance.  



The package can be unlocked with the help of the corresponding script, but unfortunately, due to security reasons, we cannot share it. If your onsite instance can be accessed from external IPs and you can contact us at support@creatio.com and grant us external access, we can unlock the package for you. 

Alternatively, you can consider deploying the onsite instance from a backup of the dev site, this way the package will be unlocked (of course if it's unlocked on dev site).

Or share with us copy of your current Database, so we'll unlock it on the copy and provide you with it.

Best regards,

Yuliya Gritsenko

Hello,



Unfortunately, it's impossible to downgrade the application. 



You can downgrade it if you made the full backup before the upgrade.



Best regards,

Bogdan 

Hello Luca,

I am not sure I understand you correctly. Can you please send an expected result and an actual result you receive?

Thank you!

Best regards,

Oscar

Hi Oscar Dylan,

I have a visual studio C# project binded to OdataV3 endpoint ("/0/ServiceModel/EntityDataService.svc/") and I don't find the custom entities created by me.

Using the following URL: "http://localhost/0/odata/$metadata" (ODataV4) I can see the expected entities.

The problem is that if I try to generate ODataV4 client code using "Unchase OData Connected Service" add-On it returns this error when I use ODataV4 endpoint.

While if I use ODataV3 endpoint with "Unchase OData Connected Service" add-On everything runs fine but the custom entities are missing (first picture). Furthermore if I use ODataV3 in a simple package every custom entity endpoint is available.

Did I make myself clear?

Thanks,

Luca

Luca Tavasanis,

Yes, it's clear now, thank you!

The problem is that OData3 forms its metadata based on the default assembly and doesn't include separate assemblies (where your objects are located), while OData4 uses a separate special assembly (neither default nor the custom one). And that's why its impossible to get access objects in packages compiled in the separate assembly using OData 3.

Our core R&D team will review this logic in the future releases, meanwhile the only way to access the object is using OData 4 only.

Best regards,

Oscar

Hello Luca,

As stated in the Academy article here: 

• It is not possible to implement object business logic via event sub-processes in the Object Designer. Use EntityEventListener to work with the event model. The EntityEventListener event set does not entirely match the event model in Creatio IDE. Learn more about the Entity event layer: Objects business logic.

And enabling the event on the object is needed for the sub-process in the object designer only. Please use the EntityEventListener instead.

Best regards,

Oscar

Hi Oscar,

I actually enabled the event on the object just to use it (as you said) in the sub-process in the object designer, but the customizations that I made there didn't work in an assembly package,  instead worked in a simple one.

Let me know if I have made myself clear or if you need other explanations.



Thank you.

Best regards,



Luca

Luca Tavasanis,

Hi,

As you said, you've enabled the event on the object to use in the sub-process in this object and did it in the assembly package. As stated on the Academy - it's impossible to use sub-processes on the object in the assembly package (and as a result the source code for the object won't be updated in case you are designing this sub-process in the assembly package). Can you please clarify what exactly is expected here?

Best regards,

Oscar

Hi Oscar,

sorry but I didn't understand that you were talking about the assembly package, my fault.

I will try the solution that you suggested with the EntityEventListener.

Thank you for your help!

Best regards,

Luca

Hi Raz,

If you do not receive any errors while you are installing the package. You can check the following points.

Bind the lookup and value correctly:

If you have the databinding tool installed on your local dev, you need to do 2 binding as:

1. Go to studio->lookup section->click on bind lookup

In the popup, select the new lookup which you would like to bind. This will ensure your object will show in the lookup section after your release.

2. In the lookup section, find you lookup (for example, ContactType), open the lookup and bind the value. This will ensure the value you bind will be released on the target site.

Please make sure the binding is unique in one package. For example, the contact type "Competitor" should be bound in the same package only once. If you have 2 binding files for the same record in the same package, you will get an error while installing the package.

Object in your package is installed and published correctly:

If you can not see your object, when you create a new lookup. Please go to the advanced setting first, and double check if the object is created already after installing the package. Sometimes you will see the object is created but you can not use it from the UI. That might be caused by the database structure need to be updated/installed.  If I get the issue like this, I always compile the site after update the structure in database, then refresh the page, or log out and log in again.

If errors are received while installing package, you need check the log file and resolve the issues in the package.

Hopefully, it will help you to resolve the issue.

regards,

Cheng Gong

Hello Andres,



Unfortunately, you can't rename the package once it is already exported, renaming the archive wouldn't change the package name itself. You can try to rename the package when it is still in the dev environment in the SQL console changing the name of the corresponding record in the SysPackage table. We don't recommend to do this, however, if it is really needed you can backup the database, change the name, generate the source code for all and compile all. After that, if while testing the functionality no errors would occur you can export the package and transfer it. 



Best regards,

Bogdan

Thanks, guess I'll create a new package with the new name and move data between old and new one.