Formula Column hitting dependency limit when there is only 1 dependency

(0) Share

Report

Posted on by EHelf

I'm running into an issue with a formula type column.

My situation is that I need to calculate a value based on the previous column value. This needs to happen 12 times.

So for example:

YOE_0=100

YOE_1=YOE_0+1

YOE_2=YOE_1+1

YOE_3=YOE_2+1

etc...

But when I try to create year 11 (YOE_11=YOE_10+1) I get an error telling me the dependency limit for YOE_0 has been reached.

When I check the dependencies for YOE_0, there is only 1 dependency. See below:

Am I missing something?

Categories:

Microsoft Dataverse with Power Apps

I have the same question (0)

All responses (6)

Answers (1)

Sort by

Drew Poggemann 9,287 Most Valuable Professional on at

Like (1)

Report
Copy link

Link copied!

Hi @EHelf ,

This is a dependency depth issue with a maximum of 10 levels deep. Example is your YEO_2 is dependent on YEO_1 which is a calculation based on YEO_0. It is a "depth" issue on the calculations you are hitting.

Would it work to not create the depth in your situation and actually do the following?

YEO_0=100

YEO_1=YEO_0 + 1

YEO_2=YEO_0 + 2

YEO_3=YEO_0 + 3

etc.?

Was this reply helpful? Yes No
EHelf 15 on at

Like (0)

Report
Copy link

Link copied!

Thanks @dpoggemann, that makes sense now.

Though I'm not sure if I can do that. I should've been more clear in the calculations happening. It's more like this:

YEO_0=100
YEO_1=YEO_0 * 15%
YEO_2=YEO_1 * 15%
etc...

So each value is calculated based on a percentage of the previous value.

Was this reply helpful? Yes No
Verified answer

Drew Poggemann 9,287 Most Valuable Professional on at

Like (1)

Report
Copy link

Link copied!

Hi @EHelf

With the limitation you could still do something like the following:

For YEO_2 as example... This would get pretty long though for others...

=(YEO_0+(YEO_0*0.15)+((YEO_0+(YEO_0*0.15))*0.15))

Was this reply helpful? Yes No
EHelf 15 on at

Like (0)

Report
Copy link

Link copied!

Hi @dpoggemann ,

So I was able to get past this problem by changing the columns to Calculated columns instead. It achieves the same and doesn't have the dependency depth problem. But now I've run into a new issue...

When I try to import the table to a new environment I'm getting this error:
I sort of understand the error message, but why wouldn't this occur for adj_yoe_8 or previous columns where the chain would already be 5 deep. Am I misunderstanding the error?

Was this reply helpful? Yes No
SurfaceWear 186 on at

Like (1)

Report
Copy link

Link copied!

This isn't a direct answer to your question but potentially an alternative approach to calculated and roll-up columns...

Where you need to do complicated calculations, I think dataflows are a better option - you can use the table as the source data for itself, add some steps to power query that perform the necessary calculations, then map the power query output to the table columns. This can be run at fairly regular intervals (maybe a few times per day if needed).

Was this reply helpful? Yes No
EHelf 15 on at

Like (0)

Report
Copy link

Link copied!

This was the right way to go. I attempted a couple other solutions first to avoid a long repetitive formula, but they didn't work. Thanks for the help!

Was this reply helpful? Yes No