Skip to main content

Hello and thank you for adding me to this group.

I am attempting to do something that on the surface appears relatively simple however I am not quite able to figure out a work around for the issue.

I am building out a bidding module to my base.

I have a Series of tables starting with "Projects" then "Bids" then "Bid Line Items" where I then roll up the total of a set of Line Item expenses "Bid Amount*" to the Bids Table. I want to use that rollup in the "Primary" field as part of a formula however I get a circular reference error.

Is there an easy way to extract that information and use it in a formula? Thank you!

 

 

I think there might be something specific to your table setup that's causing that error I'm afraid.  I tried to replicate the issue you're facing but it seemed to work fine for me:


If you could share a read-only invite link to a duplicated copy of your base with example data that would be very helpful!

I think there might be something specific to your table setup that's causing that error I'm afraid.  I tried to replicate the issue you're facing but it seemed to work fine for me:


If you could share a read-only invite link to a duplicated copy of your base with example data that would be very helpful!


A circular reference error means that one of the fields in the formula for Bid reference* is a formula that contains Bid reference*

Circular reference errors usually mean that in the chain of calculations, an output field is used as an input.

However, it is also possible to get this error when a primary field is involved, even if the primary field seems like it should only be a final calculation and not an input.

There is no easy workaround. One option is to leave the value out of the primary field and use a different roll-up of lookup to get the value in the other table. Another option is to copy the value to an editable field whenever it changes. Then use the editable field value in the formula. 

Thank you for the feedback. I'm assuming the issue is lying with the passing of lookup data from table to table since I AM able to duplicate the formula successfully in a non primary field. 

I'll most likely need to abandon the effort to include the value of the Bid in the primary field. 

As an FYI - I'm generating unique IDs based upon the original Project ID, then adding on a unique "Bid ID" and adding a unique "Line Item ID" to that so that it's clear the source project, the subsequent bid and subsequent line items. I'm not sure if that is contributing to the problem however since it works in a standard non primary field formula I'm guessing it's more of an AirTable thing.

 

 

Terms & ConditionsCookie settings