Hello.

I tried to do replicate the same situation. Activity table has a column SendDate which might be null. In business process i created a script task with the following code:

The result i got:

The values of SendDate columns in my Activity table were all null. All these values became the min value of datetime (1/1/0001 12:00:00 AM).

Your error message says that the datetime type in SQL Server has a limited range for dates it can store, specifically from January 1, 1753, to December 31, 9999. In .NET, the default value for DateTime is DateTime.MinValue, which is January 1, 0001. This default value is far outside the valid range for SQL Server's DateTime type.

After analyzing source code you provided i suggest taking a look at those lines of code and changing your sql command parameter types to SqlDbType.DateTime2:

insertCommand.Parameters.AddWithValue("@usrDate"...
insertCommand.Parameters.AddWithValue("@usrStartTime"...
insertCommand.Parameters.AddWithValue("@createdOn"...

Hope this helps

Hello,

You need to create one-to-many relations between these objects. To do this, you need to create a lookup column in each object that will refer to another object. After that, you will be able to use filters and relationships to display and customize the necessary lists.
You can't do it using no-code elements because this connection is set up at the object level.

Hello. 
I implemented similar logic but instead of opening a modal page, i open card for the detail. In case section i added a test detail. When double clicking on a record in this detail onGridRowDoubleClick method is called which set values of record to sessionStorage and opens a UsrTestCardPage. Than init method is called while page is initializing which sets the field values.

Card schema:
 define("UsrTestCardPage", [], function() {
    return {
        entitySchemaName: "UsrTestDetail",
        attributes: {},
        modules: /**SCHEMA_MODULES*/{}/**SCHEMA_MODULES*/,
        details: /**SCHEMA_DETAILS*/{}/**SCHEMA_DETAILS*/,
        businessRules: /**SCHEMA_BUSINESS_RULES*/{}/**SCHEMA_BUSINESS_RULES*/,
        methods: {
            init: function() {
                this.callParent(arguments);
                this.getSessionStorage();
            },
            
            getSessionStorage: function() {
                var UsrName_SessionValue = sessionStorage.getItem("UsrName_Session");
                var UsrIntColumn_SessionValue = sessionStorage.getItem("UsrIntColumn_Session");
                var Id_SessionValue = sessionStorage.getItem("Id_Session");
                this.set("UsrName", UsrName_SessionValue);
                this.set("UsrIntColumn", UsrIntColumn_SessionValue);
                this.set("Id", Id_SessionValue);
            }
        },
        dataModels: /**SCHEMA_DATA_MODELS*/{}/**SCHEMA_DATA_MODELS*/,
        diff: /**SCHEMA_DIFF*/[
            {
                "operation": "insert",
                "name": "UsrName2a0f6821-93ff-4f8b-a8c0-e58bb9032171",
                "values": {
                    "layout": {
                        "colSpan": 24,
                        "rowSpan": 1,
                        "column": 0,
                        "row": 0,
                        "layoutName": "ProfileContainer"
                    },
                    "bindTo": "UsrName"
                },
                "parentName": "ProfileContainer",
                "propertyName": "items",
                "index": 0
            },
            {
                "operation": "insert",
                "name": "INTEGER406f5583-84ac-4659-9ff8-46b9c72de82a",
                "values": {
                    "layout": {
                        "colSpan": 24,
                        "rowSpan": 1,
                        "column": 0,
                        "row": 1,
                        "layoutName": "ProfileContainer"
                    },
                    "bindTo": "UsrIntColumn",
                    "enabled": true
                },
                "parentName": "ProfileContainer",
                "propertyName": "items",
                "index": 1
            },
            {
                "operation": "insert",
                "name": "LOOKUPcb467c2f-f352-4ac0-90ea-f25c2ed22119",
                "values": {
                    "layout": {
                        "colSpan": 24,
                        "rowSpan": 1,
                        "column": 0,
                        "row": 2,
                        "layoutName": "ProfileContainer"
                    },
                    "bindTo": "UsrCase",
                    "enabled": true,
                    "contentType": 5
                },
                "parentName": "ProfileContainer",
                "propertyName": "items",
                "index": 2
            }
        ]/**SCHEMA_DIFF*/
    };
});

Detail schema:

Hope this helps

Hello,

Unfortunately, the basic functionality of the platform doesn't allow you to filter values specified by you. However, we've registered this idea in our R&D team backlog for consideration and implementation in future application releases. Thank you for helping us to improve our product.

Great idea :) It's like also making sure some inactive values are not only inactive in dropdowns, but also in filters. 

Hi Satyam, 
You can try using crt.7XRequest with action 'EditRecord'/ 'AddRecord'. Please see this article on community : https://community.creatio.com/questions/base-function-lookup-value-clic…

Yurii Sokil,

The Terrasoft modules are also still available. You can use the same code as in classic UI, something like this will work in a Freedom UI request: 

Terrasoft.MiniPageListener.open({
	parameters: {
		entitySchemaName: "Activity"
	},
	valuePairs: [
		{ name: "Type", value: "fbe0acdc-cfc0-df11-b00f-001d60e938c6" },
		{ name: "Contact", value: contactId },
		{ name: "Account", value: accountId }
	],
	miniPageSchemaName: "ActivityMiniPage",
	operation: Terrasoft.ConfigurationEnums.CardOperation.ADD,
	showDelay: 0,
	miniPageSourceSandboxId: null
});

Ryan

Hi Kevin, you need to disable the Feature called UseSchemaDesignPackageUIdByHierarchy. In yor instance must add this "/0/Shell/#Section/AppFeature_ListPage" after cretio.com to open the Features Page, search the feature, disable (turning off the “Is enabled” and “Is enabled for current user”), save and click on  button "Clear Cache".

Regards

Julio Falcón

Julio.Falcon_Nodos,

Are there any caveats to doing this Julio?

Gareth Osler,

This basically just reverts the behavior to use the "Current Package" system setting, even for all Freedom UI stuff. I have more info on that here: https://customerfx.com/article/reverting-the-behavior-for-saving-pages-in-the-creatio-freedom-ui-designer-to-use-current-package-setting/

Ryan

Hello!

The new package is creating if changes have been made to the application, but its main package is locked.

When developing an application, you can force the application not to create a new empty package, but to save changes to the package you created.
This can be done by disabling the UseSchemaDesignPackageUIdByHierarchy system feature - it is responsible for the logic of checking and creating a new package for the application, as well as the CurrentPackageId system setting and the Installed application and Package lookups. 

Now you will need to specify the package (recommended Custom) in the CurrentPackageId setting.

This message is referring to the data elements in your package. There are sections added to workplaces in the package (SysModuleInWorkplace) but the Workplaces they are added to are not bound in data elements in the package (SysWorkplace). To resolve, look at any data elements for SysModuleInWorkplace in your package and make sure you add a data element for SysWorkplace for the workplaces that the sections are in.

Ryan

Ryan Farley,

Thanks alot!

Greetings,
 

Could you please tell me what you mean by "why my object is not saved"? 

Hello,
The reason lies in the type (UsageType) of the RecordInactive= "Advanced" column, which is why the system does not display it in the designer. Unfortunately, there is no way to change this column type.

However, there is a workaround that will allow you to use the feature, namely the "DisableBlockingSystemColumns" feature that needs to be created and enabled for users that you need to have the rights to use such system fields.
1. Go to the link: https://SITENAME.creatio.com/0/Features
2. Add a new parameter:

3. Create a new parameter called "DisableBlockingSystemColumns", then add the role that well have the access to it, enable the checkbox and save the changes:

4. Relogin to the site.

However, this will allow users who have this option enabled to see other restricted and system columns in the system. We recommend using this approach in the "extreme" case, if the work of this functionality is critically important.

In addition, we have already created a task for our development team to fix this issue. Unfortunately, we have no exact ETA at the moment, since the task is at the initial stage, but it may be included into one of the next releases.

Hello,

To be able to see these emails, you need to enable logging in the advanced settings in the Email Sending process element. 
After that, you can find the emails in the Activity table or set up a dashboard to view them.