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.

Info here: https://academy.creatio.com/docs/user/setup_and_administration/security…

 Hello Stefano,

You can change the prefix in the SchemaNamePrefix system setting:

Hi Anastasia,

I know the system settings suggested.

I need to change the prefix for existing custom object

Hello,

There is no possibility to change its code.

We've registered it in our R&D team backlog for consideration and implementation in future application releases. Thank you for helping us to improve our product.

Definitely needed for 8.1 ?

Hi Everyone,



Is this issue sorted? is there a way to stop the random code?



Regards

Deshan

I am also receiving the same response. 

Hi 

Can someone help me?

Is there any common issue from the API side?

Thanks

I messaged support yesterday but so far no response or acknowledgement. Have you tried compiling the system and were there any errors?

Hi

I don't have access to the system

It's for one of our clients who is facing the issue

How can we contact the creatio support team?

Is there a support portal?

Thanks

Hello,



Please try using Odata 3.



More details on the academy website:

https://academy.creatio.com/docs/developer/integrations_and_api/data_se…

Hi

I see odata3 returns an XML response

Is ODATA 4 not supported hereafter?

Thanks

Hello Ivan, 

Could you please elaborate a bit on your business task?

Best regards,

Anastasiia

Hi!

So, I have 2 columns: 1 is Business Line for Legal Entity and the other one is Business Line for individual. I want the business line to be show on the even if it is for the LE or for an individual to be shown on the same column.

Ivan Rares Marian,

We create VIEW in database, create object based on that VIEW and display any information we want :)



Kind regards,

Vladimir

Vladimir Sokolov,

Can you be more specific or can you provide me a link where I can find it

in Academy? 

Thank you,

Rares Ivan

Ivan Rares Marian,

Something like this (I haven't found for latest version, but idea is the same) - 

https://academy.creatio.com/documents/technic-sdk/7-16/localizing-views



If you don't manage different language localization, you can stop at first VIEW in point 2

Dear Vladimir Sokolov,

Many thanks for your help!

Dear Ivan Rares Marian,

Please proceed with recommendations provided by Vladimir and let us know in case of any questions!

Best regards,

Anastasiia

Thanks a lot, Vladimir and Anastaia. I will follow your steps

Have a nice day!



Rares Ivan

Hi!

It's a known issue. We'll gladly provide a solution to your particular instance in case you submit a request to our Technical Support team via support@creatio.com.

Thank you!

Hello,

Please be informed that by the system's logic, the details still refer to the same object and even if you create several different details they are still based on the same object and therefore the edit pages will look the same. We already have this problem registered for our R&D department and in future releases this logic may be changed.

Mira Dmitruk,

I know they refer to the same object, are you not able to have the different details enter data slightly different? So if you enter it from one detail the type is set to "revenue" and the other "costs", otherwise id need to have a lookup to do it when it shouldn't be necessary.

Hello Oliver,

To do this (set a different type value based on which detail is being used to add the record), you can set defaultValues in each of the details in the page code. See this article here: https://customerfx.com/article/passing-values-from-a-page-to-a-new-reco…

As far as filtering each detail by the specific type value, you can refer to this article: https://customerfx.com/article/filtering-a-detail-list-in-creatio-forme…

Ryan

Hello Jose, 

There should be all packages that were there in 7.18 UI.

If you want to manually add the existing packages to the application hub - you have to create a record in SysInstalledApp package and SysPackageInInstalledApp.

Thanks Aleksei. I was able to add the applications on the app hub following your instructions. Is there any article on Creatio with steps/best practices for converting existing pages/sections from the 7.18 version to the new Freedom pages/sections?

Jose Hernandez,

Actually, it has to be done automatically, old packages should appear in the Application hub.

So, there is no article.

It may be worth investigating why the packages did not appear in the application hub.

You can keep in touch with the support and they will check possible reasons for such behavior.

hi Joseph Francisco,



Which section has this "Decision Maker" field? 

Hi,

Add below code in opportunity edit page. Let me know if you still face the issue.

{

                    "operation": "insert",

                    "name": "OpportunityDecisionMaker",

                    "values": {

                        "layout": {

                            "row": 2,

                            "column": 5,

                            "colSpan": 19

                        },

                        "bindTo": "DecisionMaker",

                        "controlConfig": {

                            "enabled": true

                        }

                    },

                    "parentName": "BantProfile",

                    "propertyName": "items",

                    "alias": {

                        "name": "DecisionMaker",

                        "excludeProperties": ["layout"],

                        "excludeOperations": ["remove", "move"]

                    }

                },

Joseph Francisco



You can use the diff code provided by Nishit Singla, with one change. Instead of Insert, please use the "merge" keyword since the insert will consider it as a duplicate entry of the same item.



The below should be sufficient to enable/unlock the field.

Also, make sure you need it in "OpportunityPageV2".

{
                    "operation": "merge",
                    "name": "OpportunityDecisionMaker",
                    "values": {
                     "enabled": true
                     },
},

BR,

Bhoobalan Palanivelu.

Nishit Singla,

This one works for me. Thanks Nishit Singla