I am looking for a way where I can share a bunch of macros consolidated as an Add-in stored in a workbook that is saved as a .xlsm, with everyone in my department. I need to maintain full control of the workbook being used, so that no one can make changes to it, but if I make changes to the master copy it will automatically update all the ones used by all the people I am sharing it with. A shared drive deploy is out of the question due to access issues.
We are using SharePoint to control access to the workbook. I am wanting to do something similar to what's described in this link but using SharePoint instead of a shared drive.
Sub Auto_Open()
Workbooks.Open ("http://sharepointaddress/Workbookwithaddins.xlsm")
End Sub
Related
I have been using excel documents containing protected ranges and hidden sheets, it seems like this can be circum navigated by importing into google sheets and likewise when doing the same in google sheets the functionality is lost when downloading as excel.
I understand the principles behind why this happens but I am curious as to whether there is any way of keeping this functionality?
I am afraid it is not possible since both are different technologies. Microsoft's protection works with the file itself while Google's protection checks the permissions from each Google account.
Not long ago Google added a compatibility mode for office files so you don't have to convert the files to Google Docs to open them, however this view still has limited features and it is not possible to work with the same type of protection in both platforms.
Reference:
Work with Microsoft Office files
Edit Office files
I have an Excel script created in my Office Online account. I see where I can share that script with another user per workbook and also where I can share the script with another user as a whole in the manage access section of the .osts file itself.
I need the script to be accessible to an entire user - not just per workbook - so I've shared the .osts file with the second user.
That user can see the file in their shared files, but if they open an Excel file, it is not listed in their scripts. How do we get the shared .osts file to appear in the Automate tab when they open any workbook?
At this point, Excel only shows the scripts that are either (a) present in user's own OneDrive folder (documents/Office Scripts) or the ones shared on the workbook. We are working on enabling SharePoint based storage that you can use to share with everyone on the team and users can open it from their taskpane. For now though, the scripts can only be shared in the Excel workbook level.
Microsoft now allows scripts to be saved in SharePoint so that other users of the SharePoint site can access them. Script-storage
(Desktop version) I'm new to using the javascript API for excel, but is it possible to create an excel add-in and share with other users without having to add the add-in to an app source etc? Can it be embedded in the excel file etc. I'd like to share scripts with other users the same way that I can share VBA if it's possible?
for security reasons as well as to make manageability of your add-ins easier, we do not store the code within the workbook, like VBA. Instead, the javascript is hosted on your website and we have a reference to your add-in saved in the workbook.
What this means, is to get a similar experience to VBA, you must either have the add-in hosted on app source (which will make it accessible via the Office Store), OR each user in an organization must have the add-in deployed or available to them (here we recommend centralized deployment as it will give the most robust experience).
This has all the current deployment options you can use for Office add-ins: https://learn.microsoft.com/en-us/office/dev/add-ins/publish/publish
thanks!
Currently we have a shared excel add-in created in-house and stored on a shared server. However if I want to make changes to this, everyone who has the macro installed has to close excel even if they aren't using the macro currently. Even on a small team this is difficult to accomplish.
Is there a way that I can make changes on a draft/beta/development version and "push" those changes to the main file?
Many thanks!
My team and I share this workbook on a network drive. This workbook utilizes a few custom add-ins necessary for some custom functionality. These add-ins get automatically installed by custom VBA code I have added without any action on the part of the user. It seems that only I can use the add-ins - other team members have problems trying to load the add-ins, they get this error:
Run-time error 1004 Unable to copy add-in to library.
The error occurs when trying to run
Application.AddIns.add(<addin_name>)
The add-ins are located only on the Windows network share. I've written the code to ignore the prompt for copying the add-in to addins folder on local drive, because I don't want this to happen. This is a very annoying problem because I cannot debug it fully myself, I need the cooperation of my team members which is limited. Help greatly appreciated, thanks.
I would suggest just opening the XLA read-only from the network drive as if it was a workbook (which of course it is) rather than using Addins.Add - opening an XLA makes it available to the Excel session so it will function as an addin without being in the addins collection.