Upgrade Project Using API Loses Last View as Starting View

[CoderBoy]

I've done quite a bit of searching on this topic and can't find a workaround.

It appears that when a project that was saved in an older version of Revit has the starting view set to <Last Viewed> (the default setting) if you use the API to upgrade and re-save a project in a later version of Revit, this information is lost and the next time the upgraded project is opened by a user in the newer version of Revit it reverts to a floor plan view.

This is at least true with the current release, Revit 2017.

Apparently this does NOT happen if upgrading the project manually using the Revit GUI.  It also appears that if, in the old project, the user had set the Starting View to a specific view, after upgrading with the API to the new version of Revit that specific view *is* still the starting view.

The problem only seems to appear when the Starting View had not been specifically selected by a user in the old project, and the API is used to upgrade the project to a new version.

It appears that once the API has upgraded the project in the new version of Revit, the information about whatever was last viewed is lost.  Also, we can not find a way to determine what that was so we could restore that information manually in code.  There seems to be no good workaround for this situation that we can find.

As such, I would like to submit a Wish List item to Autodesk to have the API upgrade process retain the <Last Viewed> view from the older version of Revit that saved the file being upgraded, and respect that as the starting view the next time the upgraded project is opened by a user.  

This requested update to the API would not *change* the Starting View to that view, the Starting View would still be set to <Last Viewed>, but it would simply no longer forget what the <Last Viewed> view was during upgrade via the API.

Thank you very much.

[jeremytammik · Accepted solution]

Dear CoderBoy,

Thank you for your very valid request and eminently lucid explanation.

I submitted the wish list item CF-4715 [API wish: upgrade and re-save RVT in a later version should retain the starting view] on your behalf for the functionality you suggest, as this issue requires exploration and possibly a modification to our software. Please make a note of this number for future reference.

You are welcome to request an update on the status of this issue or to provide us with additional information at any time quoting this wish list item number.

This issue is important to me. What can I do to help?

This issue needs to be assessed by our engineering team, and prioritised against all other outstanding change requests. Any information that you can provide to influence this assessment will help. Please provide the following where possible:

• Impact on your application and/or your development.
• The number of users affected.
• The potential revenue impact to you.
• The potential revenue impact to Autodesk.
• Realistic timescale over which a fix would help you.
• In the case of a request for a new feature or a feature enhancement, please also provide detailed Use cases for the workflows that this change would address.

This information is extremely important. Our engineering team have limited resources, and so must focus their efforts on the highest impact items. We do understand that this will cause you delays and affect your development planning, and we appreciate your cooperation and patience.

Could you please also submit this to the Revit Idea Station?

http://thebuildingcoder.typepad.com/blog/2016/05/idea-station-and-textnote-bounding-box.html#2

Once you have done that, you need to ensure that it gets many votes.

That is currently the newest primary driving force for Revit development.

Afaik, 50 votes is a good target.

Submitting all API wishes there was mentioned all over the place at RTC, AU, ADN DevDays, and other recent events:

http://thebuildingcoder.typepad.com/blog/2016/10/rtc-revit-api-panel-idea-station-edit-and-continue....

http://thebuildingcoder.typepad.com/blog/2016/11/devday-conference-at-autodesk-university.html#4

http://thebuildingcoder.typepad.com/blog/2016/11/au-day-one-keynote-and-devlab.html#6

http://thebuildingcoder.typepad.com/blog/2016/11/au-day-two-ifc-and-revit-api-panel.html#6

I hope this helps.

Best regards,

Jeremy

[CoderBoy]

Hi Jeremy. 

Thank you for submitting this item.

I forgot about Idea Station (it seems like about every year or so Autodesk comes up with a new way to submit feedback...).  I have submitted this on Idea Station as well, using the API tag.

Oddly, I received at least 4 emails from Autodesk telling me this support case was closed.  I found that odd, but as long as there is an awareness for this wish by the development team, that's what's really important.

Regards. 

[jeremytammik]

Dear CoderBoy,

Thank you for your update, appreciation and submitting to the idea station as well.

Sorry about the continuously new paths to provide feedback. I hope they help improve the universe in the long run.

I guess the four email were generated automatically by the system each time the status of the internally generated and associated ADN case 12534074 [Upgrade Project Using API Loses Last View as Starting View] changed.

Ah yes:

• First, I closed the internal case myself, marking it as a change request.
• Secondly, you closed it by marking my answer to this thread as an accepted solution.

That accounts for two emails. The factor of two (four emails instead of two) is presumably negligible.

I hope this clarifies.

Indeed, the only important things are the internal development database issue, the entry in the Idea Station, and the number of votes that receives.

Best regards,

Jeremy