nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

.NDVLSNVLSDNVJDS

demand forecast the result is a circular reference screen

Tags

Accepted answers

@olhmexve - The circular reference error occurs when you to try to refer the original line item to where you are actually putting the formula.

It would be great if you could provide the screenshot of the error you are facing.

All comments

@olhmexve
Can you explain in detail or provide screenshots for reference.

@olhmexve - The circular reference error occurs when you to try to refer the original line item to where you are actually putting the formula.

It would be great if you could provide the screenshot of the error you are facing.

Quick Links

Can you help?

Unanswered questions

I need to flow data from a model DAT01a in PBF Dev to PBF Consol
I need to flow data from a model DAT01a in PBF Dev to PBF Consol, we use connectors to do this OUT3A and OUT3B Any instructions or tips on how to build or test the data can be flowed through to PBF Consol?
User story 3.3 To derive Monthly Commission Forecast
Hi, My values of monthly commission forecast is not matching the Check your build values. Please help to identify where I am wrong. As I have attached screenshots of the blueprint and module grid view. Thanks, Sre Varshaa S
Handling Month–Year vs Year–Month format issues in Anaplan imports?
In our current setup on a Global Engagement, most regions use a Month–Year format (e.g., Jan-26) for the time range in the forecast upload template. However, the US region follows a Year–Month format (e.g., 26-Jan) in their local Excel files. This mismatch creates a challenge: When US users download the template, it is…