Weird behaviour of the dataFile.publicLink property

[Anonymous]

Hi support / forum,

We are using a python script to update a list of URLs to all files in a given Fusion 360 project. In doing so, we recursively inspect all folders and whenever a relevant file is "detected" we make a call to the property "DataFile.publicLink" described below:

http://help.autodesk.com/view/fusion360/ENU/?guid=GUID-86975614-B402-4117-9DD4-024C688F3666 

The issue we have is that every time we make a call to this property, it generates a new URL, making the old publicLink address invalid (this is a problem as we use these links in Monday.com to manage our documentation work). This is further complicated by the fact that - seemingly - any update to the file in mention (e.g. a 2D drawing) also updates the URL.

Can someone please explain the behaviour of this API call to "DataFile.publicLink"  and indicate how a more static behaviour can be achieved, where the URL is not updated unless I want it to be updated?

Any help would be greatly appreciated. Thanks!

[kandennti]

I tested it. Certainly it changes every time.
Is it related to security ...?

Text command

NuCommands.SimpleSharingPublicLinkCmd

Or API

_app.executeTextCommand (u'NuCommands.SimpleSharingPublicLinkCmd')

When you execute, a dialog appears and publicLink is displayed.

This doesn't seem to change after running it multiple times.

However, unfortunately, I don't know how to get the publicLink displayed here.

[Anonymous]

Thanks for the reply @kandennti.

I suppose this is becoming more of a feature request in that it would be nice to specify whether a call to the "dataFile.publicLink" property should update the URL or simply provide the existing URL. The former seems to be the only option at this time.

Similarly, it would be nice if an option was provided where edits to the file did not cause an update to the URL.

[prainsberry]

Hello,

I completely understand this need.  Let me look into a few options for you and I will reply back to this post soon.  We are working on some thing related to this right now and might have a different approach for you.

[Anonymous]

Brilliant, @prainsberry ,

Very much looking forward to seeing what you come up with. Any workarounds / feature tweaks would be very helpful. Thanks in advance.

[prainsberry]

The team did some digging and it looks like the API was not properly handling the backend response when a share link already exists, and thus generated a new one.  We should be able to get a fix in place reasonably soon.

That said I would be very much interested to talk more with you about your application?  This type of workflow is something I am looking at very closely right now.  Would you have time for a brief chat this afternoon or next week sometime?   Can you send me an email at: patrick.rainsberry_at_autodesk.com?

[Anonymous]

Hi @prainsberry ,

Thanks for the follow-up. I have just sent you an email.

[goyals]

Created ticket FUS-74558 to track it. The fix would be available in Fusion Dec. release. Thank you for posting this issue.