I created a multi select lookup page for a detail in freedomUI using "crt.OpenLookupPageRequest" functionality. I wanted to either remove already selected records in the popup window or show them as checked if they are added into the detail.
I have a subprocess that loops the returned records from an API call and adds a new record in a data object. I want to modify the process to check if the record already exists and if so, modify the existing record with the data changes.
First read the record using whatever Identifier you have on it from the source data. If the record exists the Id value will be a Guid and if it doesn't exist the Id of the record will be Guid.Empty.
So the condition for the update will look like:
[Id from the Read] != Guid.Empty (this means the Read found the record)
The "else" will proceed to the Add, just make sure you populate some identifying value from the API call that you'll use when you read if the record exists next time.
I am looking to data import for the product section and detail objects using a single excel template. In the contact and account sections, we have the option to import the additional address details.
Is that possible to get additional detail objects like this for the product section?
Allow me to clarify how the import process works. When importing data into Creatio, you are essentially transferring the information from your Excel file into the corresponding database table. Each detail in Creatio corresponds to a different object or database table. Therefore, during an import, data can be inserted into one table or object at a time.
Import to Contact/Accounts have custom core logic applied, but all other objects work with logic described above.
what is your experience or recommendation about deleting custom field from the object?
If some fields were added by mistake and the package was already installed to another evirnoment. Is it ok to delete such field and install the package again? Or should we keep this 'garbage' in the object forever?
You need to remove it from the development website, install the package on the production website, and the package installation mechanism on the production site will detect the differences in objects between what exists in production and what is in the package, and drop them.
You need to remove it from the development website, install the package on the production website, and the package installation mechanism on the production site will detect the differences in objects between what exists in production and what is in the package, and drop them.
On the opportunities product page, when I select a product, the price is filled in automatically. However, I've deleted the business rules and scripts on the opportunity product page.
My problem is that this price includes tax, even though the PriceWithTaxes parameter is unchecked in the system settings.
I've set up a script to enter the price excluding tax but from time to time it's the price including tax that appears (probably an asynchronism problem).
I'd like to know where the script that enters the price of the opportunity products on the page is and how I can change the behaviour.
Finally we found the problem: the OpportunityProductPageV2 source page in the Opportunity package contains a method that calculates the price of the product including VAT: calculatePrice.
I've overridden the method and the problem is solved.
I thought that creating the OpportunityProductPageV2 page in the Custom package replaced the view model, but in fact it's an extension.
Finally we found the problem: the OpportunityProductPageV2 source page in the Opportunity package contains a method that calculates the price of the product including VAT: calculatePrice.
I've overridden the method and the problem is solved.
I thought that creating the OpportunityProductPageV2 page in the Custom package replaced the view model, but in fact it's an extension.
It depends on which column should be required here. One particular example: this method can be added to ActivityMiniPage:
save: function(callback, scope){
var opportunity =this.get("Opportunity");if(opportunity){this.callParent(arguments);}else{
Terrasoft.showInformation("Opportunity is required");}}
In this case saving of the mini page is not possible in case an opportunity is not connected to an activity and the information message will be shown on the page.
If you need to display across the system only those contacts created by the users themselves, this can be achieved by configuring record permissions. If you toggle the switch but do not specify any roles, records will only be visible to the users who created them. You can also set up such access rights based on roles.
If you want contacts across the system to be visible only to those set as the Owner of that contact, you can utilize a business process with the "Change access rights" element. Configure it in a way that when the owner changes, all access rights to the record are removed, and only the new owner is added.
If you need to display contacts in a specific field where the owner is the current user, you can use a filtering business rule to display only those contacts where "Owner" = "Current User owner".
I'm facing an issue with Creatio running on .NET Core. Occasionally, when I create a web service and make a mistake, I come across an error page like this:
The challenge is that there are no logs saved regarding this issue. Consequently, I lack information about what went wrong, and I try to guess.
On the other hand, if I attempt the same operation on a .NET Framework running instance (e.g., in the Cloud), I receive an exception stack trace.