Revit API 2022 links not showing on BIM360

Revit API 2022 links not showing on BIM360

victor.bastidas
Enthusiast Enthusiast
483 Views
3 Replies
Message 1 of 4

Revit API 2022 links not showing on BIM360

victor.bastidas
Enthusiast
Enthusiast

Hi everybody. 

 

So, I got a weird issue... I'm using Revit 2022 API, and I have some GUIDs that I obtain trough APS on a different program. 

My issue is: I link my models as an attachment, then synchronize and publish, but those models don't show up in BIM360. Then, if I open the cloud model (the links show up correctly in a 3D view), I sync manually using Revit's UI, and then publish using Revit's UI, and then I can see those links. 

 

I don't change anything in the Revit model when I open it manually, I just sync and publish manually and then the links show up. 

 

This is how I'm trying to link them and sync it. As you can see, I set those links as attachments.

victorbastidas_0-1684170345723.png

 

Do you guys have any idea if I should be doing something else before syncing and publishing? 

 

I've already tried adding a regenerate before syncing but it didn't do anything. 

 

My link models GUIDs are Revit Cloud models obtained from IFC files. 

 

Thanks and have a nice one!

 

Víctor

0 Likes
484 Views
3 Replies
Replies (3)
Message 2 of 4

jeremy_tammik
Alumni
Alumni

Sounds weird and tricky. I asked the development team for you.

  

Jeremy Tammik Developer Advocacy and Support + The Building Coder + Autodesk Developer Network + ADN Open
Message 3 of 4

victor.bastidas
Enthusiast
Enthusiast

Hi Jeremy, thanks for the help!

 

I found a pretty hit or miss workaround which is, after closing the document: re-opening the same document, syncing and then I send the order to publish on APS. 

 

As I said, it's pretty hit or miss, I'll maybe add some more open-sync-close steps in a loop and see if I get a more consistent output. 

 

Thanks again, Jeremy! Have a nice day!

0 Likes
Message 4 of 4

GeorgeKerwood
Autodesk
Autodesk

Hi @victor.bastidas,

I'm encountering exactly the same behaviour myself. Did you by chance ever resolve this issue or find a stable work-around? I apricate that it was some time ago and you would of likely posted it if you had.

Many Thanks 

0 Likes