Null Date in Source Column for External Object Type Data Source Application creates issue with property definition. How to solve it?

Hi Nafis,

In the JSON code you can add a line for targetPropertyDatatypes and specify the types allowed for the property. You can find a list of datatypes here: https://developer.m-files.com/APIs/COM-API/Reference/#MFilesAPI~MFDataType.html

By default Date is not allowed, but if you add Date to the allowed list, M-Files will accept dates. Here is an example (datatype 5 is Date):

{
"sourceColumnName": "\"Create Date\"",
"sourceType": 129,
"objectTypeMappingType": "Property",
"targetPropertyDatatypes": [1,13,9,10,2,8,5],
"targetProperty": "PD.CreateDate",
"ordinal": 9
},

Hello, Thank you for your answer. Is it possible to set this JSON property globally? Otherwise I have to edit so many columns one by one?

Don't think so. However, I have not had the need to use the code lately. It seems that it is not a problem on new versions of M-Files. Is your M-Files server up to date?

Please note that the extra line is only required on date columns. No need to do anything for other data types.

I tried this approach for only my date columns and It did not work for null date. Maybe I have to handle null check myself in code.

N.B: my Mfiles server is up to date.

You should be able to configure SQL Select to replace Null with a valid empty value using a "case - when - else" statement.

You should be able to configure SQL Select to replace Null with a valid empty value using a "case - when - else" statement.