Goals not always working - number of calculated fields?

(0) Share

Report

Posted on by Community Member

We have been using goals reasonably successfully, but have now noticed that all current goals are no longer updating.

When you open the goal itself it shows the error "number of calculated fields in query exceeded maximum limit of [goal name]

Any idea what is causing the goals to fail?

Is there a limit on anything inside the goal entity?

I know there is a limit of 100 rollups per organisation, but I am assuming the rollups inside the OOTB goal entity do not eat into this limit as if you have multiple sales people, and goals are used monthly, you very quickly use this limit up.

Many thanks

*This post is locked for comments

I have the same question (0)

All responses (8)

Answers (1)

Sort by

Suggested answer

Wayne Walton 13,730 on at

Like (0)

Report
Copy link

Link copied!

Are you running goals on calculated fields? Not just rollups, but calculated ones? If so, that sounds like your problem. You might need to set up some intermediary fields to contain the calculated field as static data, then set your goals against those instead.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report
Copy link

Link copied!

Interesting- I think I see your logic there - so set a workflow to copy the calculated fields to static ones and track the goals on them?

Was this reply helpful? Yes No
Verified answer

Wayne Walton 13,730 on at

Like (1)

Report
Copy link

Link copied!

Correct. Remember, Goals are basically a purpose-built rollups, and have the same limitations:

· A rollup can't reference a calculated field that uses another calculated field, even if all the fields of the other calculated field are on the current entity.

· The rollup can only apply filters to the source entity or related entities, simple fields or non-complex calculated fields.

Was this reply helpful? Yes No
colinbell83 on at

Like (0)

Report
Copy link

Link copied!

Hi, I have this same issue, i moved the Total Amount to a plain custom currency single field and it is still happening, i have removed the majority of Calculated fields from the opportunity entity so it is definitely not to do with the maximum 10 calculated fields per entity but it is still giving this error?

Has anyone been able to resolve this when there are no calculated fields in the query?

Whats strange is when using a Customer Entity and not the Opportunity Entity it works fine?...

any help would be much appreciated

Was this reply helpful? Yes No
yleclerc 1,549 on at

Like (0)

Report
Copy link

Link copied!

@colinbell83 Did you ever find a solution for this? I have the same problem and can't figure it out.

Was this reply helpful? Yes No
Colin365Bell 40 on at

Like (0)

Report
Copy link

Link copied!

Hi kind of, I found it was to do with the maximum number of Calculated fields across the environment. I believe you can have a maximum of 100 "Custom" Calculated fields across the environment and I had reached that. luckily i had some Calculated fields that where historical and was able to remove them

Was this reply helpful? Yes No
yleclerc 1,549 on at

Like (0)

Report
Copy link

Link copied!

Thanks!

This makes a lot of sense.

I actually can build Goals around on some entities (Sales order work fine) but not on Opportinities. In Opportunities, we have 20 calculated fields, so I guess there is a limitation per entity as well.

Most of these fields are managed, so I will have to find something else ;)

Was this reply helpful? Yes No
Suggested answer

yleclerc 1,549 on at

Like (0)

Report
Copy link

Link copied!

UPDATE

In the MSCRM_CONFIG Database - DeploymenProperties table, there is an entry called EntityCalculatedFieldLimit. Default value is 10.

As soon as we updated this value to 20, everything worked as expected. We will monitor this to make sure this doesn't cause other problems.

20 is the number of calculated fields we have in the Opportunity Entity.

We are using version 8.2 on-premise.

Was this reply helpful? Yes No