"Detected potentially damaging errors in the table", "Empty cell found"

meGVGMF
Advocate
Advocate

"Detected potentially damaging errors in the table", "Empty cell found"

meGVGMF
Advocate
Advocate

Hi,

 

Looking for some insight as to what might be wrong with an assembly that, when saved, shows the following dialog:

 

meGVGMF_0-1700767679115.png

 

Not sure what to make of this. Searching for the initial message plus "empty" has turned up nothing.

 

Thanks

0 Likes
Reply
448 Views
6 Replies
Replies (6)

Gabriel_Watson
Mentor
Mentor
0 Likes

meGVGMF
Advocate
Advocate
Thanks very much for the response.
But if my browser names are entirely clear of the symbols < and >, is this still applicable?
I believe that to be true, although I haven't looked at the files in months and can't while my coworker is still using them for the moment, but I figured I should clarify that point in the meantime.
0 Likes

Gabriel_Watson
Mentor
Mentor
The article responds to a slightly different issue. But you should be able to check the Excel sheet if there are indeed empty cells.
0 Likes

johnsonshiue
Community Manager
Community Manager

Hi! Please share the Inventor files here. It would be easier to explain why the errors come up. I guess either the table was edited incorrectly or there was an iLogic rule changing the table undesirably.

Many thanks!



Johnson Shiue (johnson.shiue@autodesk.com)
Software Test Engineer
0 Likes

meGVGMF
Advocate
Advocate

Hi @johnsonshiue
Sadly I can't share the files; however I can point to this previous, possibly related issue I posted about a few months ago, regarding the same set of files:
https://forums.autodesk.com/t5/inventor-forum/parts-list-prevents-drawing-document-from-opening/m-p/...

 

Is there a resource you can recommend regarding best practices for working with the document and model state API? We've long since stopped writing directly to the model state table, because that gave us no end of issues since migrating to 2023, where previously we had performance gains. Now we open the document and use the returned object, activating each model state as necessary and changing things like material, parameters and iProperties.

 

What might be the safest set of practices for handling these objects through that lifecycle? In all my searching I've never found a definitive answer. Perhaps you of all people might have encountered something.

 

Any help you can provide would be much appreciated. Thanks

 

0 Likes

johnsonshiue
Community Manager
Community Manager

Hi! Please share the files with me directly johnson.shiue@autodesk.com. I am more than happy to sign any NDA and we can accommodate any region server requirement and access control. Without seeing the files, there isn't much I can do unfortunately.

Many thanks!

 



Johnson Shiue (johnson.shiue@autodesk.com)
Software Test Engineer