Bim 360 Upgrade Model

[Elnora Heidrick]

Wecurrently check the models and drawings for any changes following an upgrade, so far we have not found any differences. Other companies I've spoken to are doing the same thing. I'm questioning if this a worth while exercise?

On (rare) occasions I have found that during upgrading the newer Revit version had some issue with particular families (was notified during the upgrade process) requiring to let Revit delete that family from the project. First modifying/replacing the family in original Revit version usually resolves the issue.

If you accidentally open a 2016 project from Revit 2018- as you may know, it automatically upgrades the model to 2018 and the only way to "revert" it back to a 2016-friendly state, would be to restore the .rvt file to an earlier date (and of course risk losing work)

Is there a setting related to file-opening, in which Revit will actually PROMPT YOU to let you know "hey, this is an older version- should I upgrade? PS- this can take like an hour and it will basically swallow your soul and the last shred of your patience for technology. By the way, there's no safe way of undoing this. Sincerely, Autodesk."

2019 when you select the file it tells you what version it was created in....but as for making it yell at you...find John Pierson at Parallax....he might be able to build you something. He's the one that created a popup nagging you that you clicked the Model In Place button.

There is NOT a way to prevent this from happening. In 2019 you can see the version of the file from file explorer preview. That may prevent some accidental openings, but is by no means 100% foolproof.

Only problem with the cancel button is that it doesn't always work. Today was the first time I was able to cancel because I smashed that cancel button as soon as I realized what was happening. Last time this happened, I hesitated and hit cancel maybe 5 seconds into the process and it still upgraded anyway...

You can easily upgrade all your Revit cloud models in Document Management to the latest version of Revit, using the Project Admin module. Revit models uploaded directly from Document Management are not upgraded.

During the upgrade, project members can continue to access the project and view the models. However, any changes made to the project during this time are not saved because the project version itself is updated during this process.

If you see a message indicating you need Revit Cloud Worksharing, contact your software or contract administrator to request access to Revit Cloud Worksharing, which you will need to proceed to the next step.

Read the confirmation message and click Upgrade Revit cloud models to confirm your decision. You should now see a series of messages indicating the progress of the upgrade. You will also receive an email confirmation that the upgrade has started and may take some time.

The Test Upgrade Report shows only Revit cloud models that contain errors or warnings after being upgraded. If there are no errors or warnings associated with a model, BIM 360 generates a message reading "Test upgrade complete - Cloud models in this project could be upgraded from Revit 20xx to Revit 20xx."

Storm surge can devastate coastal communities. The first version of the P-Surge model, released in 2008 by NOAA's Meteorological Development Laboratory, was galvanized by the significant impacts of storm surge on communities along the Outer Banks of North Carolina and southeast Virginia following Hurricane Isabel in 2003.

P-Surge brings a probabilistic approach to the modeling of storm surge by generating a range and likelihood of possible storm surge values. It is run in advance of hurricanes and tropical storms that may impact the Atlantic and Gulf coasts, and now Puerto Rico and the U.S. Virgin Islands.

I've seen an earlier thread discussing the same error, one suggesting that the absence of a model descriptor folder can be an issue, and the apparent MS issue thread, but I don't think I'm encountering either of the first two, so hope someone could please offer guidance. Example of models that can't be found: (1) "ApplicationSuite.VAR Model" (2) "ApplicationFoundation.VAR Model".

Having gone through the AX 2012 > D365 code upgrade & configured my mappings, I'm at the point of attempting to load the CodeMergeSolution or UpgradedSolution VS projects from the Relase folder created in Azure DevOps. When I get latest on the Metadata folder, the Visual Studio output window shows that it's getting objects such as AosService\PackagesLocalDirectory\ApplicationFoundation\ApplicationFoundation.VAR Model\AxTable\Delta\PrintMgmtReportFormat.xml or AOSService\PackagesLocalDirectory\ApplicationSuite\ApplicationSuite.VAR Model\AxTable\Delta\VendTable.xml which suggests to me that the code upgrade has created "sub models" within the standard Application Suite or Application Foundation models. Should I be trying to merge these change 'down' to the standard models somehow? I'm pretty confident this isn't yet at the point of merging into the Main branch, though the instruction "If you are migrating from Dynamics AX 2012 R3 or earlier, you will be mapping to the metadata folder under the Main branch." within Configure VSO solution mapping section leaves an element of doubt.

Thanks Nikolaos, Sukrut. The disappointment of not being given more assistance by the code analysis/upgrade tools is somewhat offset by your reassurance that I'd correctly decided how much is down to the developer... After my previous reply, I did find this blog series that discusses the conflict resolution option, but since that leads to overlaying, I think that's somewhat outdated.

Resolving conflicts has to be done manually using compare tool . No external tool is going to help you with that . For creating extensions and other development task you can quickly perform using below tool

Thanks for correcting my wording Nikolaos: having done some extension development in a greenfield D365 instance, I could have phrased that better & appreciate your specifically pointing to extensions. I'd tried refreshing the models from the Dynamics 365 > Model management menu item, but was hitting the invalid reference/circular dependency issue others have discussed & resolved by editing the descriptor xml for the "submodels". Mentioning that in my first post may have been helpful...

I can now open my projects and am starting to work my way through conflicts & merges. Feel like I'm probably not making best use of the automated tools Microsoft provide, so if anyone has read any good material on resolving conflicts & merging code, I'd gladly accept any pointers.

You can't change the standard modelsx so "down" is not the right direction or your code. Instead, reimplement all overlayerings (which is in Delta folders) into extensions. Then move these extensions to a new package / model. Eventually all your elements must be in your own packages, not in models inside standard packages such as ApplicationSuite.

The models you are referring are created because you have overlayering in those objects. When you run upgrade tool from LCS after all migrations steps are done finally all code is brought at overlayered code and different models are created within those packages , during model split.

Your next task is to start your work in your Main branch to resolve the conflicts and removed code from these standard packages and move it as a extension. Once you are ready with all your code in your own packages and application is error free , you can rename this branch to dev branch and work on your branching strategy.

Fitted with the smaller 60-kilowatt-hour battery pack, my car's EPA range of 208 miles was not quite enough to make it between Superchargers--Tesla's proprietary ultra-fast DC charging stations--at normal Interstate speeds in cold weather.

I could extend the car's range by driving 60 mph in the slow lane, with the heat off, or loiter in the customer lounges of Nissan dealers along the way, while my car picked up the extra few miles it needed courtesy of their slower Level 2 charging stations.

Not for buying a Model S--not at all--but for not ponying up the extra $8,000 to specify the larger 85-kWh version of the Model S, withan EPA range of 265 miles, which could have covered the distances between Superchargers with ease.

Well, it now appears that Fate has smiled upon me. In an example of exquisite timing, I received an unexpected end-of-year financial windfall. And my tax guy strongly recommended that I spend some of it before December 31.

That proved to be the rub. After I expressed interest in the deal, a Tesla sales rep was able to come up with only two standard 85-Kwh inventory cars (not the pricier Performance model). But both were very low-mileage, well-equipped cars that cost as much or more as the new one I'd priced.

But I didn't want to wait indefinitely, watching my trade-in value decline by $2,000 a month. And I didn't want to end up paying for popular options I didn't want, like a moonroof or a premium sound system.

Yes, I was assured, I'd get that added kick. The motor and inverter systems in the two models are physically identical, I was told, but 60-kWh cars are software-limited to 302 horsepower, against 362 hp for 85-kWh cars. Why? The smaller battery isn't safely able to deliver the necessary current to provide 362 hp.

I had hoped that the trade-in value of my old battery would be prorated for its actual use--10 months and 11,000 miles out of its guaranteed life of eight years and 125,000 miles. This would have amounted to about a 10-percent "restocking fee" rather than the actual 20 percent

3a8082e126