Error in import

[JENVDC]

I get this error when I import my model, it’s not a problem in other programs, (Bimcollab Zoom/ Dalux)

Can someone explain what this means

[Patric 0]

@JENVDC : Open File with ‘Note’ and Change Text entry . It hears Like a simple Problem with your Partname.

[JENVDC]

Hi Patric, thanks
what would you change the text into :

#89360=IFCWALLSTANDARDCASE(‘1ql0L6zyn5DfgueP8NKDOJ’,#20,‘Basic Wall:Inderv\X\E6g-110mm - Gips--Gips_AN.229.001_Nedrivning:11317817’,$,'Basic Wall:Inderv\X\E6g-110mm - Gips--Gips_AN.229.001_Nedrivning’,#89348,#89359,‘11317817’);

[sarahhielscher]

Please do not make any changes to the IFC file, as this will compromise the trustworthiness of the overall data. Moreover, it does not permanently solve the causal problem.
This is an export problem. When exporting, the authoring software generates a character that does not correspond to the ASCII code. This leads to a lexical error.
Please check your export settings and, if in doubt, contact the support of the authoring software to avoid such errors in the future.

Such lexical errors should never be ignored, as they can cause major problems in the long run. An example would be that in a few years the model is to be opened for a new use case with software that also detects lexical errors and refuses to open it. Then you need the original file from the authoring programme to correct the error. Correcting the IFC has the massive disadvantages already mentioned and should never be done. If the file from the authoring programme is then no longer available, the model loses all its usefulness!

Such lexical errors can be “corrected” internally by software solutions during import. Solibri deliberately does not do this, as it is a quality assurance software and lexical errors must be corrected from this point of view.

[Matti]

@sarahhielscher @JENVDC

Thanks for the report. We are working on improving the Solibri IFC string decoding.