Cross posting from Stackoverflow because it hasn't been updated to indicate whether it was fixed or not and I do not have the ability to comment on Stackoverflow.
https://stackoverflow.com/questions/51661308/excel-js-online-settings-not-persisting-past-session
@dmahugh @JuaneloJuanelo - Can you comment on this here and/or Stackoverflow.
Settings should get persisted using the Excel Specific API's when using Excel Online.
The Excel specific settings API was not working about 3-4 months ago. The stack overflow linked above mentioned it was a bug and to use the older Office shared API. My team scrambled to switch over to this and it is currently working using the Office Shared API.
See stackoverflow post but try saving some settings using Excel Specific API and Excel Online and you will see that it doesn't save them when returning to the file. If you then switch to the Office Shared API it will persist between sessions.
We changed our code based on the suggestion in the Stackoverflow thread and it now uses the shared API's. New year so we are trying to get our code based cleaned-up so we would like to revert back to the Excel Specific Api's for consistency across our code base.
Excel Online - All browsers.
@LanceEa thanks for reaching out about this. @JuaneloJuanelo are you able to provide an update regarding that status of the bug that Lance describes?
still working on a fix and btw you have a workaround as described on stack. please use the workaround for now. thanks!
@JuaneloJuanelo - Thanks for the update. Can we please leave this open so that once resolved it can be commented on here? AFAIK, there is no subscribe feature in stack overflow unless you participate (comment, answer, etc...).
This way I will get notifications from Github and know that we can revert the code.
Thanks,
Lance
Re-opening this issue per @LanceEa request.
It seems like I am observing the same problem on the latest version of office.js - sometimes the changes would not persist back to the workbook despite explicitly awaiting for Excel.run() and context.sync(). I am now trying the shared API to see if things get better using it.
Has this been solved, or should the workaround be used in the meanwhile?
Also, @dmahugh @JuaneloJuanelo I think you meant to re-open this issue but it was never re-opened :)