Deleting calculated fields not needed

(0) Share

Report

Posted on by DianeF1

210

We are cleaning up our application (long story) and we have quite a few calculated fields. We are able to delete fields like spirit_totalvaluecosts but we are unable to delete spirit_totalvaluecosts_base. When we try to delete the now not referenced field spirit_totalvaluecosts_base we get the error "This field contains a calculated money value and cannot be deleted. Select a different field and try again".

Is there any way to get these fields that are no longer in use out of the system?

Regards,
Diane

*This post is locked for comments

I have the same question (0)

All responses (6)

Answers (1)

Suggested answer

Kristian Cole 290 on at

Like (0)

Report

1. Try removing it from the form first.

2. Then delete the field from the field section of your solution.

Was this reply helpful? Yes No
Suggested answer

TheMarkChristie 10,328 Moderator on at

Like (0)

Report

Hi Diane

I would open the field form the solution and check to see if there are any dependancies on it. If there are not i may suggest a workflow that clears the value of this field

Was this reply helpful? Yes No
Georgy on at

Like (0)

Report

That's quite strange behavior. I would recommend you:

1) Publish full solution.

2) Try again.

It's just a guess, assuming that you deleted the main field, the _base one should have deleted by itself.

Was this reply helpful? Yes No
DianeF1 210 on at

Like (0)

Report

I deleted the main field and published. The _Base field remained and when you try to delete the _Base field the error stating

"This field contains a calculated money value and cannot be deleted. Select a different field and try again. " comes up. So now I have a _Base field that has no big brother field

Was this reply helpful? Yes No
Verified answer

Georgy on at

Like (0)

Report

I've faced similar issues (in D365 only!) with rollup fields. As I told before, what we did:

1) publish all

2) remove the fields from any solution apart from default.

3) delete the field in default solution.

as suggested above, try looking for dependencies.

(I'm sure it's a stupid assumption, but could it have been that you acidentally "removed" the big brother field, rather than deleting it?)

Was this reply helpful? Yes No
Suggested answer

DianeF1 210 on at

Like (0)

Report

Taking that second look and showing some one else did the trick. I have several fields that are VERY CLOSE in name. I did my delete on spirit_totalnrevaluemargindiscount with the next field being spirit_totalrevaluemargindiscount (the difference is total nre vs. total re). When I looked closer - YES!!! the field with nre in it was gone and I'd mistakenly missed that.

Thank you for making me double check :)

Diane

Was this reply helpful? Yes No