Importing Solution - Error while importing Calculated fields

[DanFou]

I'm attempting to import a solution in another environment. However, I'm getting the following error:

• Error while importing Calculated fields name cr55d_plannedisd

The field itself is working correctly in the other environment.

[ChrisPiasecki]

Hi @DanFou,

Is there any further detail of the error message you can provide? You should be able to download the Import log XML and open in it in Excel. The 2nd sheet should should show a line by line detail of each component import status and eventually you should come up on the calculated field that failed to import and its error message. 

---
Please click Accept as Solution if my post answered your question. This will help others find solutions to similar questions. If you like my post and/or find it helpful, please consider giving it a Thumbs Up.

---
Please click Accept as Solution if my post answered your question. This will help others find solutions to similar questions. If you like my post and/or find it helpful, please consider giving it a Thumbs Up.

[DanFou]

@ChrisPiaseckiI did have a look at the XML file provided. It features very little info, see attached file.

Edit: Sorry, just noticed your comment about the second sheet. Looking at that now!

Edit 2: Got a bit more info:

0x8006043A

You can only use a Date Only type of field.

Edit 3: I looked at the datatypes, all the dates involved in the formula are Date Only. The field plannedisd is also Date Only. Here is my formula:

[ChrisPiasecki · Accepted solution]

Hi @DanFou,

Can you verify if the Behaviour of all the Date fields used in the calculated field also match? E.g. are they all "User Local"? While strangely it may not break in your source environment, it will fail to import to another environment.

As per the docs on Behavior and format of date/time field:

Warning:

Before changing the behavior of a date and time field, you should review all the dependencies of the field, such as business rules, workflows, calculated fields, or rollup fields, to ensure that there are no issues as a result of changing the behavior. After changing the behavior of a date and time field, you should open each business rule, workflow, calculated field, and rollup field dependent on the field that you changed, review the information, and save it, to ensure that the latest date and time field’s behavior and value are used. You can restrict modifying the field’s behavior, by setting the CanChangeDateTimeBehavior managed property to False. More information: Set managed property to change date and time behavior

---
Please click Accept as Solution if my post answered your question. This will help others find solutions to similar questions. If you like my post and/or find it helpful, please consider giving it a Thumbs Up.

[DanFou]

I switched all the date fields (Date Only) to have the matching Behavior of Date Only and was able to import my solution. Thanks!

[ChrisPiasecki]

Glad that worked for you @DanFou, Happy Friday!