When I try to export the data from a 2018.1.1 file with RevitDBLink, the program doesn't recognize the materials of the file.
This happens with a Collaboration for Revit model. I think there is a problem with the materials in this kind of model.
We use the SQL Server 2008R2
Hi,
Looks like you are a product question. Not API. I'm going to move this to Revit product forum.
https://forums.autodesk.com/t5/revit-architecture-forum/bd-p/133
@pgutierrezm86 Can you confirm if the issue is specific to models stored on the Collaboration for Revit service, by saving the model locally (detach) and then checking if the warning occurs?
Also, it would be helpful if you could attach a journal file recorded when the warning shows up.

Hi Lance,
Yes, I've tried with a detached file, but when it comes from a collaborate model it happens the same way.
I attach a journal from a collaboration model.
Thanks any kind of help!!
Thank you for the update.
In reviewing the journals, I’m not seeing one where the model is being saved locally (both seem to show the C4R model being opened and then the DBLink command run).
Could you try opening the C4R model, save to a new name (Save As) locally, and then try running the DBLink command again (after closing then re-opening the locally saved model)?
If the issue continues, then I would want to look at the journal file created.

I attach the files from a local file.
Thank you Lance.
Thank you for the update.
When I look at Journal.0076.txt (locally saved model), I am seeing different information compared to the previously provided journals.
In the original journals, I’m not seeing the error/warning from the screenshot (the journal stops during the export process). However, In the latest journal (0076) it looks like the export is successful.
I am seeing a line about warnings, but nothing like the screenshot of the error:
' 1:< TaskDialog "There were warnings during exporting/importing"
Are you seeing the same error when exporting the locally saved file?
Also, it may help to test disabling worksharing entirely and removing the 9 missing links encountered (this would leave the model in a more consistent state, and should eliminate any connection to C4R).

Sie finden nicht, was Sie suchen? Fragen Sie die Community oder teilen Sie Ihr Wissen mit anderen.