I can’t find anything on this anywhere. But I had the same problem a year ago in the. solution that I finally worked out then doesn’t seem to be working this time. I’m guessing the numbers in brackets are an array address, but I’m not sure. Anyway, when I “Run Autocat” I get this error.
I just added about a dozen Category/Description combos to the AutoCat sheet and now have 984 rows there. I have 90 Categories defined. When I deleted the Category/Descriptions I added, the error persists. Arggghh!
If you can help with this one, I will buy you a beer (or your favorite beverage < $20)
Hello @wetmore55, just a thought in case you’re working out of OneDrive or SharePoint: have you tried checking Version History in Excel? If the AutoCat sheet was working fine before your latest updates, you might be able to roll back to a version from before the issue started.
Feels like there may be a mismatch in the range after deleting rows. You can go to the Tiller console and create a new spreadsheet for a fresh sheet with the formulas. Rename the original categories sheet and import the fresh one. Copy and paste the AutoCat rules. Certainly a stab in the dark I’m taking.
-Alice
Tiller Evangelist
Bluesky, Instagram, Facebook, LinkedIn
Alice,
Thank you very much for your suggestion. Yes, I’m using OneDrive and I had not thought of your idea. So I gave it a try. But surprisingly, it didn’t work. So I went back again several days before the “run AutoCat” problem cropped up, and it still occurred. Which suggests something else is going on. Separately, I had built a new clean file from the foundation just prior to my most recent problem only a couple of days before the AutoCat problem surfaced and initially things worked well, so go figure…
When I had this problem a year ago I think I resolved it by reducing my number of Categories or my list of Category/Description pairs. But maybe I was mislead and the real problem was there was a Description that was causing the problem (i.e. I deleted it as part of a pair, and maybe the pair had a nonprintable character or somesuch).
I have had a vision problem the last few days which blocked me from PC work, but it’s better now so I will start digging again.
I appreciate your help.
Rich
Hi @wetmore55 how’s the digging going? If the issue persists you might need to share your file with support to take a closer look. You can write to support@tiller.com
Twalane,
Thank you for nudging me. An unrelated problem is that my vision is only good enough about two days a week to work with my PC, due to an MS symptom. but I read your message this morning and I could see well enough to complete my digging, and now things are working. unfortunately, I had to go back and start with a completely new foundation file and rebuild everything. but it is working. if I have the problem again I will take your advice early on and call for some help from support.
If nothing else, I’m very curious what the [0,0,1,16384] refers to. That knowledge might have led to a quicker diagnosis.
Thank you,
Rich Wetmore
Hi @wetmore55 glad you got it resolved that way. Sometimes the error is misleading and one just has to look more closely at the configuration or setup.
Wishing you continued wellness! Indeed, do not hesitate to reach out to the support team next time.
