** The problems decribed below in this post from April 2021 have been addressed in the May 2021 release of Ideate Sticky. Please read the updated blog post for the latest details.**


Re-Branding of Autodesk BIM 360 Impacts Ideate Sticky

A recent change to the Autodesk Desktop Connector includes a re-branding of Autodesk’s BIM 360 platform. This change is described in the recent Desktop Connector Release Notes with important highlights that relate to Ideate Software, as shown in the image below. 

Autodesk BIM 360

When your end users install this version of the Desktop Connector, the change will manifest locally as a renamed folder. What was previously “C:\Users\[user name]\BIM 360” will become “C:\Users\[user name]\ACCDocs.” 

This change may impact Ideate Software customers. Please read below for per-product implications.

Ideate Sticky

For those of you using Ideate Sticky and storing your Excel, Word, or PDF files on BIM 360, you will find that this change will result in broken file paths for Ideate Sticky. We recommend the following steps, in order of importance:

  1. Avoid updating to the Desktop Connector if possible. We will re-code Ideate Sticky to support this change. We hope to release Ideate Sticky within 60 days of the Revit release.
  2. If you cannot avoid doing the update, then you will want to select all Stickies within each project and update them to the new path location. Here is a video with instructions.

Ideate Automation

Ideate Automation will work fine with the file path change. However, if you have customized your Ideate Automation scripts and those scripts are writing Excel file content to a BIM 360 path, you will need to adjust your script to use the new file path.

For example, in the image below, the original script has caused a new folder called “BIM 360” to be created. To avoid this problem, you should edit your existing script and do a search for “\BIM 360” and then do a replace with “\ACCDocs” path.

Help us Improve

We strive to integrate our solutions into the Autodesk eco-system wherever possible. In this case, our ability to handle this change is limited by the lack of a formal Application Programmer Interface (API) for the Autodesk Desktop Connector. You can let Autodesk know this is important by voting for this idea on the BIM 360 API forum.