Is the Forge Model Upgrader Example Deprecated? - autodesk-forge

I have connected the Forge Model Upgrade example to my BIM 360 hub.
https://forge.autodesk.com/blog/design-automation-revit-projectfamilytemplate-upgrader-sample
Currently, it does not work.
Is it possible to get it to work?

From comments: the live version works for 2019 models (as designed), but can be modified to support other versions. Output needs to be in a different folder.

Related

View BIM 360 & Fusion models Unable to load model:Failed to load resource: net::ERR_NAME_NOT_RESOLVED

I did it according to the example on the official website, but the model couldn't be loaded。I don't know why, I followed the tutorial, and I checked the API should be open normally,I think I need help. Here's a screenshot of the error;
I see two possible explanations for this type of error:
The model is coming from A360 or Fusion Teams. If that's the case, please note that models uploaded to these applications are not translated automatically by the Forge Model Derivative service (hence the viewer error stating that there are no "viewables" to load). You have to open the designs in their owning application first to initiate the translation process, and then you can try accessing them from your own Forge application.
It's possible that the sample application is having issues with some of the characters used in the file names. Check if the same error happens when you name your files using English alphabet.

Upload models to BIM360 Design, not BIM360 Docs

I'm able to successfully batch upload Revit models to BIM360 Documents (and version them, as well). However, my main goal is to be able to batch upload models to BIM360 Design as our day-to-day (pre-published) design models.
It appears that instead of using type items:autodesk.bim360:File that I should be using items:autodesk.bim360:C4RModel. However, I keep getting "The client_id is not whitelisted for schema items:autodesk.bim360:C4RModel." Is there a way to provision my app to access that?
As a user, I have admin rights to BIM360 Docs, so I don't think it's an individual rights issue.
Thanks!
It’s not possible for you to upload “cloud” models with a
Forge app. It can only be done with a Revit Addin today.
Unfortunately, Forge DM API doesn't support enabling C4R model currently. However, you can do that with Revit API with Revit desktop, see here for the details: https://thebuildingcoder.typepad.com/blog/2019/11/initiating-bim360-collaboration-and-linking.html#2

How to view model offline using autodesk forge viewer?

I have also tried sample project from Git
https://github.com/Autodesk-Forge/viewer-javascript-offline.sample
Which is not working either.
Is it possible to see model offline in viewer?
Thanks in advance.
As the latest take on running Forge applications in "disconnected" workflows, we've posted an article on our blog that shows the usage of Progressive Web Application standards like Service Workers or Cache API: https://forge.autodesk.com/blog/disconnected-workflows.

What version of Revit does AutodeskForge support?

When converting the file created by Revit 2014 to SVF, the following error occurred:
The file was saved in an old version of Revit which we don't support.
Please upgrade this project to Revit {0} or later.
I found out that the Revit version is old.
I do not know the range of versions of Revit that AutodeskForge supports.
Does it matter if Revit 2016 or later?
The minimum supported version is Revit 2015. Sorry for not having this information available at the website. It's only shown on https://viewer.autodesk.com, when you click the link called "2D and 3D formats".

What changes were made to the IBM Worklight JSONStore API between versions 6.1 and 6.2?

It appears that as part of the transition from IBM Worklight 6.1 and 6.2, changes were made to the JSONStore API. Specifically, it looks as if the load() method (along with others) were deprecated.
It appears that the replacement for this approach is to instead use the change() API that's part of JSONStoreInstance to refresh data from an adapter call (i.e. syncing it from the backend), and to mark it as "clean" along the way. I make this inference from the most recent versions of the JSONStore tutorial for MobileFirst Platform 6.3.
However, this change to the JSONStore isn't discussed in the "what's new in 6.2" section of the Knowledge Center, as far as I can spot.
Can someone confirm this is indeed the intended change? Is there any more information on what changing with JSONStore support between 6.1 and 6.2 publicly available?
Working with JSONStore and external data in v6.2 is documented here. There are APIs for transactions (i.e. startTransaction, commitTransaction, rollbackTransaction). There are security utilities here. There's an advancedFind API that uses QueryPart objects and other find API improvements (i.e. filter, sort). There's also a native JSONStore API for Android and iOS with examples here. The structure of the documentation changed and new sections got added (e.g. general terminology) while some old sections got updated. There's a way to enable the collection of analytics information (e.g. file size, operation time) from JSONStore (Android & iOS, hybrid & native) to the Operational Analytics console, that's documented here. There are also hybrid JSONStore APIs for Windows Phone 8 and Windows 8.
The changes are all intentional.