Index/Match Formula refresh issues
I have many formulas that use a default value if they return an error from an Index/Match. Well today during a meeting everything was returning a default value. I went to troubleshoot after the meeting and slowly the Index/Match values are starting to appear if I manually save sheets with the source data.
=IFERROR(INDEX({Summary AccountName}, MATCH($Account@row, {Summary Account}, 0)), DefaultDesc@row)
I did just move large amounts of data from multiple sheets to other sheets. Maybe forumla recalulation is metered so as to not impact overall performance?
Thanks for your thoughts. Mike
Best Answers
-
Depending on the size of your sheet(s) and the scope of your changes, it could take a while for the updates to be made. I have a sheet that will auto-fill a formula into a new row as soon as it is created, but the output itself does not appear for anywhere from a minute to upwards of 20 minutes sometimes because there is so much happening.
-
Happy to help. If it continues, try logging out, clearing cookies and cache, then logging back in. If it is STILL happening, I suggest reaching out to support. There may be some bad data on the back end that needs refreshed.
Answers
-
Depending on the size of your sheet(s) and the scope of your changes, it could take a while for the updates to be made. I have a sheet that will auto-fill a formula into a new row as soon as it is created, but the output itself does not appear for anywhere from a minute to upwards of 20 minutes sometimes because there is so much happening.
-
Thanks! This is good to know. I think my issue is made worse by accessing report data from excel using the data connector. It was refreshing fine this morning. I was introducing a new field into older data files and I was checking as added it to each year of data. Sometime around noon it started acting up. First time this has ever happened so I'm not worried yet. I'll monitor over the weekend.
-
Happy to help. If it continues, try logging out, clearing cookies and cache, then logging back in. If it is STILL happening, I suggest reaching out to support. There may be some bad data on the back end that needs refreshed.
