Microsoft Dynamics CRM (Archived)

Import unmanaged solution failed : You can only use a Date Only type

(0) Share

Report

Posted on by Community Member

Hi,
im trying to import unmanaged solution into Dynamics 365 on premise and getting the below error on custom field

Error_5F00_importingSolution3V2.2.png

Please suggest help. Much appreciate if you would respond quickly.

*This post is locked for comments

I have the same question (0)

All responses (6)

Answers (1)

Syed Ibrahim 6,257 on at

Like (1)

Report

Did you tried to change the Date field as Date only instead of Date and time?

Was this reply helpful? Yes No
Suggested answer

RaviKashyap 55,410 Moderator on at

Like (1)

Report

Hi Mohannad,

This issue occurs if you have a calculated field of date & time and within the formula you have used another field which has a different behaviour than this field.

For example, assume you created a calculated datetime field and set it to ADDDAYS(5, createdon) whose behaviour is set to "Date Only". Now by default createdon field's behaviour is "User Local" so there is a mismatch.

Interestingly, in your source environment, even with this mismatch it will continue to work but you won't be able to move the field as solution and you won't be able to change the calculated field formula (unless you remove createdon field)

I would suggest you to verify this for your field and then change the behaviour accordingly.

** Do not that if you set the behaviour to Date Only, you won't be able to change it back. So review your requirements before changing it.

Hope this helps.

Was this reply helpful? Yes No
Suggested answer

Nithya Gopinath 17,078 on at

Like (1)

Report

Hi Mohannad,

If the custom field which is throwing error is a caculated field, make sure the behaviour of the date time fields used in calculating that field are the same in the target environment.

See: technet.microsoft.com/.../dn832103.aspx

technet.microsoft.com/.../dn946904.aspx

Note: All DIFF functions require that the first Date and Time field and the second Date and Time field have the same behavior: User Local, Date Only or Time-Zone Independent. If the behavior of the second field doesn’t match the behavior of the first field, the error message is shown, indicating that the second field can’t be used in the current function.

Hope this helps.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Much appreciated Ravi,

But the problem is that the behavior of the custom field is Date-Only and the action i am using is Now function (which will set the value of that custom field with the current Date-Time ). Since its Date Only behavior how can i modify it ?

Or what do you suggest any other solution ?

Thanks,

Was this reply helpful? Yes No
Verified answer

RaviKashyap 55,410 Moderator on at

Like (1)

Report

Hi Mohannad,

If I am not wrong, even the Now functions returns datetime so you won't be able to set it to field with behaviour set to "Date Only". And you can't change the behaviour from Date Only to something else once it is saved.

So the options I can think of is to add a new field and set the date using JavaScript. Now you can either use this field instead of the existing field or if you have to use the existing field due to some dependencies then change the calculation of existing field and set it to the new field.

Hope this helps.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Yes that what i was thinking of. I have deleted the field and created new and set the date using JavaScript.

Much appreciated Ravi

Was this reply helpful? Yes No