Hello,

As far as we understand,  you are referring to the fact that the "Mulai Bekerja" field is not available for selection in the formula setup.

This is most likely because Creatio currently supports only numeric fields in business rule calculations. Date fields, such as "Mulai Bekerja," are not supported in this context.

Please let us know if you'd like assistance implementing this logic using a business process instead.

Valeriia Hromova,

i have already tried using the business process however am unable to find the year function, so i would like some support here

Michael Fernando Handoyo,

Hello,

Thank you for your follow-up.

You're correct — business rules in Creatio do not currently support date fields in formulas. However, when working with business processes, you can calculate the difference between dates using the C# DateTime structure, as described in the documentation:

https://academy.creatio.com/docs/user/bpm_tools/business_process_setup/formulas/process_formulas#title-1621-4

Also, we have this built-in function that may help you as well:

Substract one number from another, divide it by 30 (if you need months) - here is your result in months (or you can use other math functions from the article)

It depends on what exactly you need. If you want to take a value from one field, perform an arithmetic operation with field B, and store the result in field C when the value in the first field is specified, you should follow the approach described in this article: https://customerfx.com/article/responding-to-an-event-when-a-field-is-changed-on-a-creatio-freedom-ui-page/, assigning the value as explained in this article: https://customerfx.com/article/programmatically-determining-the-bound-attribute-for-an-object-property-in-a-creatio-freedom-ui-page/.

Oleksandr Tyra,

Hi, 
thanks for your answer, sorry but i still confused, For example, I input field a is 1000 and field b is 2000, for field c will be filled automatically by adding field a and b to 3000, is that possible? And what is the step?
 

thanks

muhammad rizky,

Hello,

as of version 8.2.2, you can use the new business rule formula feature of the "set field value" action.

Before that, you would either create a business process that does the calculation (if live updates are enabled on the entity, the result will immediately show up on the form after saving), or programmatically, as Oleksandr has described it.

muhammad rizky,

{
    request: "crt.HandleViewModelAttributeChangeRequest",
    handler: async (request, next) => {
        // listen for changes to the EmployeesNumber field
        if ((request.attributeName === "UsrStringField_A" || request.attributeName === "UsrStringField_B") && !request.silent) {
            //var fieldA = request.$context.getAttributeNameByViewItemName("UsrStringField_A"); -- or like this
            //var fieldB = request.$context.getAttributeNameByViewItemName("UsrStringField_B"); -- or like this
            const fieldA = await request.$context.UsrStringField_A;
            const fieldB = await request.$context.UsrStringField_B;
            request.$context.UsrStringField = fieldA + fieldB;
        }
        return next?.handle(request);
    }
}

Oleksandr Tyra, Robert Pordes, 
 

Thanks for your advices, i will try it first 

Hello,

Please describe in more detail what code you wrote (if possible, provide an example), what it is for, and how it's connected to business rule and import.

Team,



Any insight on this?





Regards,

Bhoobalan Palanivelu.

One approach you can take is to add a subscriber to the detail. It is a function you can add to the detail definition to receive add/edit/delete updates from the detail. I believe that is possibly how it is working now out of the box. 

Locate the detail and add a subscriber like this: 

details: {
    ProductInProductsTab: {
        schemaName: "OrderProductDetailV2",
        entitySchemaName: "OrderProduct",
        filter: {
            masterColumn: "Id",
            detailColumn: "Order"
        },
        subscriber: { methodName: "refreshAmount" }
    }
}

Then add the function:

methods: {
  refreshAmount: function() {
    // refresh or do something since the detail has had something added/edited/deleted
  }
}

Ryan

Hi, 

This logic may be quite difficult to follow, and due to that I recommend you add breakpoints in the network to see it for yourself, but if you want a small step-by-step explanation then here it is:

When you are changing the product values the system triggers the method onBaseQuantityOrUnitChange in the schema BaseProductDetailPageV2? after it calcDiscountAmount, calcTaxAmount, and calcTotalAmount also start in this schema. Then the method saveRowChanges from the schema OrderProductDetailV2 and following the chain of methods we get to refreshAmount from BaseOrderPage and updateAmount/updateAmountFromDB from ProductEntryPageUtils. After that, triggers a modifyAmountESQ/updateAmountColumnValues from BaseOrderPage and in the end calls updateAmountColumnValues from ProductEntryPageUtils which is setting the "Amount" column.

I know I missed quite a lot of steps but it's really better to inspect this logic for yourself using breakpoints.

Hello,

You can try creating an integer column in the page (and in the object that this page represents) and create a business process that will change the value in this column once the record is added to the detail (or decrement once the value is removed). This way you can create the logic without additional code that will save resut in the server.

If you still want using the code - something similar is the functionality of the order product detail summary (that displays the number of products in order, can be found on the order page in the "products" tab). This logic can be found in the updateSummary method from the OrderProductDetailV2 from the Order package.

Hi Morgan,



Indeed, there are no articles about calculated fields on a detail.



When a detail is created, there are two schemas created: detail schema and page schema. On the page schema of the detail you are able to work with attributes just like in the section. For example, you have a detail with editable list, you can create a calculated field logic (attribute with dependencies) on the detail page and logic will be working properly when you are modifying records in the detail grid.



If we are talking about your case, when you need to update some values based on a page field after detail is loaded, I think the best approach will be following:

1. Pass the value from the page to the detail. You can do that using sandbox messages or default values of the detail. Default values - is property that is passed from the page to the detail and is specified in defaultValues block. For example:

 

"UsrSchema7Detailff9f268f": {
	"schemaName": "UsrDetailSchema",
	"entitySchemaName": "usrDetailObject",
	"filter": {
		"detailColumn": "UsrMainObject",
		"masterColumn": "Id"
	},
	"defaultValues": {
		"SectionAttributeName": {
			"masterColumn": "DefaultValueName"
		}
	}
}

On the detail, you can handle both message and default value on the init function. DefaultValueName you will be able to get from this.get("DefaultValues") object. Once you get the value, set its value to some attribute.



2. Once you have the value that is used for calculations, you can override function prepareResponseCollection and use your value for calculations. This sample is on the community here.



Hope it helps!

Regards,

Dmytro

Thanks Dmytro, I'll try this method out

Please check if you have the value of system setting called "Prefix for object name" set as Usr and if it is not - you need to change it to Usr and relogin to the system and check the issue after that.

If it won't work, please try to find this column in the database and if it is not present in the database - please run update database structure for the object which is represented by the table where this column is present.

Also please double check if the field was added the same way to this part in the article:

define("OrderPageV2", [], function() {
    return {
        // Edit page object schema name.
        entitySchemaName: "Order",
        details: /**SCHEMA_DETAILS*/{}/**SCHEMA_DETAILS*/,
        // The attributes property of the view model.
        attributes: {
            // Name of the view model attribute.
            "UsrBalance": {
                // Data type of the view model column.
                dataValueType: Terrasoft.DataValueType.FLOAT,
                // Array of configuration objects that determines [UsrBalance] column dependencies.
                dependencies: [
                    {
                        // The value in the [UsrBalance] column depends on the [Amount] 
                        // and [PaymentAmount] columns.
                        columns: ["Amount", "PaymentAmount"],
                        // Handler method, which is called on modifying the value of the on of the columns: [Amount] 
                        // and [PaymentAmount].
                        methodName: "calculateBalance"
                    }
                ]
            }
        },
        // Collection of the edit page view model methods.
        methods: {
            // Overriding the base Terrasoft.BasePageV2.onEntityInitialized method, which 
            // is triggerd after the edit page object schema has been initialized.
            onEntityInitialized: function() {
                // Method parent implementation is called.
                this.callParent(arguments);
                // Calling the handler method, which calculates the value in the [UsrBalance] column.
                this.calculateBalance();
            },
            // Handler method that calculates the value in the [UsrBalance] column.
            calculateBalance: function() {
                // Checking whether the [Amount] and [PaymentAmount] columns are initialized
                // when the edit page is opened. If not, then zero values are set for them.
                var amount = this.get("Amount");
                if (!amount) {
                    amount = 0;
                }
                var paymentAmount = this.get("PaymentAmount");
                if (!paymentAmount) {
                    paymentAmount = 0;
                }
                // Calculating the margin between the values in the [Amount] and [PaymentAmount] columns.
                var result = amount - paymentAmount;
                // The calculation result is set as the value in the [UsrBalance] column.
                this.set("UsrBalance", result);
            }
        },
        // Visual display of the [UsrBalance] column on the edit page.
        diff: /**SCHEMA_DIFF*/[
            {
                "operation": "insert",
                "parentName": "Header",
                "propertyName": "items",
                "name": "UsrBalance",
                "values": {
                    "bindTo": "UsrBalance",
                    "layout": {"column": 12, "row": 2, "colSpan": 12}
                }
            }
        ]/**SCHEMA_DIFF*/
    };
});

p.p1 {margin: 0.0px 0.0px 0.0px 0.0px; font: 12.0px 'Helvetica Neue'; color: #454545}
span.Apple-tab-span {white-space:pre}

You can use this function: 

        numberOfDays: function(date1, date2) {

                if (date1 instanceof Date && date2 instanceof Date) {

                    var oneDay = 24 * 60 * 60 * 1000; // hours*minutes*seconds*milliseconds

                    var diffDays = Math.round(Math.abs((date1.getTime() - date2.getTime()) / oneDay));

                    return diffDays;

                }

                else {

                    return 0;

                }

            },

I hope it works for you.