@ThatBIMGuy@jklempau Yes, The ADSK system is set up so that you can "self-serve" if both domains have SSO enabled. However, it does not at all support integrating a non-SSO enabled company into an SSO enabled company.
Note for future me: Step One, enable SSO if not on and use AD to update emails.
@JacobWSmall @AMWatkins26 I need you to forcibly cram the software development, REST, and various ACC API information I need to do my ACC housekeeping in an efficient manner into my brain.
@JacobWSmall@Twiceroadsfool@tkunsman I like the way #BimBeats has their system set up. The end user machine pushes data up to a central location and you have dashboards that mine all the data. It’s really quite impressive. Been fighting for years to get a company positioned correctly to take a stab at adoption.
@JacobWSmall@tkunsman Yeah that’s what I assumed. You can see if they sync’d. But if they didn’t leave any sync there’s no evidence (besides the borrowed elements that a user was in the model.
@Twiceroadsfool@NsikanAbasiUtuk That may quite possibly what I was experiencing. It’s not an everyday workflow for me. But I have found the Rubicund seems to be around Revit 18.
I upgrade stuff directly all the time. But I have had models that won’t open past a specific release. So you do a two step upgrade.
@ThatBIMGuy@tkunsman I had the user in question (a BIM manager) go in open the file with an audit and SWC with a compact.
I wanted to make 100% sure she was out of the project and if it comes back we’ll call Scooby and the Gang!
@NsikanAbasiUtuk Yeah that’s a direct upgrade. Which i believe has a higher probability of failure for every year between old and new Revit versions. I had a really old RVT 2015 file that would only upgrade to 2018 which was the oldest available at the time. Then we went from 2018->2023.