Outlook Desktop, Office.context.roamingSettings.set does not work about office-js

[ndeleuze]

@DmitryKostochko I have followed your repro steps for a newer (17505.20000) and older (17126.20190) build of Outlook and I'm not able to reproduce this issue.

Would you be able to provide a video of the issue?

[DmitryKostochko]

I have just reproduced the issue with Version 2402 (Build 17328.20162).
To what email address should I send the video?

[ndeleuze]

@DmitryKostochko are you able to post the video on this thread?

Also, does this issue reproduce in more recent builds?

[DmitryKostochko]

@ndeleuze, please have a look:

roamingSettings-set-saveAsync-get.mp4

If you have any questions or need more information, feel free to ask me.

[ndeleuze]

@DmitryKostochko thank you for the video.

I'm still unable to reproduce this issue. (I also tried to repro this on build 17328.20184 with no luck)

Just to confirm, are you able to retrieve the roaming setting when the taskpane is not first closed?

[timwan10]

Hm, I'm also not able to repro. I tried the exact steps, in the inspect debugger as in your video. Is it possible there is something else your add-in is doing in OnReady/Initialize that is affecting settings? (I do know this is probably unlikely).

can you try in Script Lab (downloadable from the store), and see if the problem repros with this add-in as well?

What happens if you immediately get the value without refreshing or saving?

Is it possible for you to step into roamingSettings.set ? To see if anything is failing? (it might be helpful you use office.debug.js instead of office.js)

does Save return any errors?

Office.context.roamingSettings.saveAsync(function (asyncResult) {
		 if (asyncResult.status == "failed") {
			console.log("Action failed with error: " + asyncResult.error.message);
                  }
		 else {
			 console.log("Settings saved with status: " + asyncResult.status);
		 }
});

[DmitryKostochko]

@ndeleuze, closing and opening the taskpane is required because of:

The persisted changes will not be available until the task pane (or item in the case of UI-less add-ins) is closed and reopened.
https://learn.microsoft.com/en-us/javascript/api/outlook/office.roamingsettings?view=outlook-js-preview#remarks

[DmitryKostochko]

@timwan10,

Hm, I'm also not able to repro. I tried the exact steps, in the inspect debugger as in your video.

Could you please provide a video of what you are doing? This could help me spot the difference between yours steps and mine.

can you try in Script Lab (downloadable from the store), and see if the problem repros with this add-in as well?

The bug is reproducible with Script Lab.

What happens if you immediately get the value without refreshing or saving?

The get method works in this case.

does Save return any errors?

I don't see any errors.

If you have any questions or need more information, please let me know.

[ndeleuze]

@DmitryKostochko here is my attempt at reproducing this issue:

Recording.2024-04-10.174345.mp4

This is with build 16.0.17328.20282, but I am still not able to reproduce your issue. Please let me know if you find any discrepancies between your repro and mine.

Are you experiencing this issue on new builds?

[DmitryKostochko]

@ndeleuze, thank you for the video, your steps seem correct.

But I have just reproduced the issue with 16.0.17425.20124 32-bit version.

What Outlook bitness do you have installed?

May it be that you have another Outlook window with the "Script Lab for Outlook" pane open? Please try to restart your Outlook and then execute the Office.context.roamingSettings.get method.

[ndeleuze]

@DmitryKostochko I unfortunately do not have a 32-bit version that I can test against, but I am certain that I do not have another Script Lab pane open when attempting the repro.

What is the business impact of this issue? Number of users impacted?

[DmitryKostochko]

@ndeleuze I just tested the issue with the 64-bit version and can confirm that it is reproducible.
Version 2404 (Build 17531.20120 Click-to-Run)

What is the business impact of this issue? Number of users impacted?

This bug seriously affects our users.