inconsistent sessionData.getAllAsync return value

[b-tosic]

Hello,

Is sessionData.getAllAsync supposed to return a dictionary?
At least documentation is not clear https://learn.microsoft.com/en-us/javascript/api/outlook/office.sessiondata?view=outlook-js-preview#outlook-office-sessiondata-getallasync-member(1)

it states: "Gets all session data key-value pairs."

It seems that when sessionData is empty it returns string '{}' (not an dictionary object).

Here is a code snippet to reproduce the issue:
`
Office.context.mailbox.item.sessionData.getAllAsync((asyncRes1)=>{
let allData1 = asyncRes1.value;
let type1 = typeof allData1; // 'string' <-- we got a string '{}' not an empty dictionary object

Office.context.mailbox.item.sessionData.setAsync("something123", "someval1", (asyncRes2)=>{
    Office.context.mailbox.item.sessionData.getAllAsync((asyncRes3)=>{
      let allData2 = asyncRes3.value;
      let type2 = typeof allData2; // 'object'  <--now we get dictionary

      Office.context.mailbox.item.sessionData.removeAsync("something123", (asyncRes4)=>{
              Office.context.mailbox.item.sessionData.getAllAsync((asyncRes5)=>{
                let allData3 = asyncRes5.value;
                let type3 = typeof allData3; // 'string'    <-- again when it is empty we got a string
              }); 
          });
    }); 
});

});
`

I'm running this in Outlook taskpane in Compose window.

Or should I do some initialization so that sessionData is always initialized to object.
Please advise.

Kind Regards,
Bojan

[b-tosic]

I apologize, but for some reason code formatting doesn't want to format code snippet correctly in my question above (it did not format first 3 lines as code).

[AlexJerabek]

Thanks for raising this question @b-tosic.

@samantharamon, could you please take a look?

[samantharamon]

Hi @b-tosic,

Thanks for reporting this behavior. The getAllAsync method should return a dictionary object, so when no session data is set on the item, the call should return an empty object (Outlook on the web returns this type correctly). This bug in classic Outlook on Windows is currently being tracked in our internal backlog using the internal reference number 9768247. We'll update this post once the issue has been resolved.