search

OfficeDev / office-js

A repository for issues related to the Office JavaScript APIs and Office Add-ins platform. Find the Office.js library in Office.js CDN: https://appsforoffice.microsoft.com/lib/1/hosted/office.js.
https://learn.microsoft.com/javascript/api/overview
Other
725 stars 106 forks source link

CustomProperty not shared between web and app in Outlook Addin #5467

Open JongHwaPark opened 1 month ago

JongHwaPark commented 1 month ago

Provide required information needed to triage your issue

I am developing an Outlook Add-in and using CustomProperty to store data specific to each email item. However, I have noticed that CustomProperty values are not shared between the web and app versions of Outlook. This behavior seems inconsistent and might be a bug.

Your Environment

Expected behavior

Current behavior

Steps to reproduce

  1. In the app, compose an email and set a CustomProperty using the Add-in, then send the email.
  2. In the app, check the sent email in the Sent Items folder and verify the CustomProperty value using the Add-in. The value is correctly displayed.
  3. In the web version, open the same email and try to retrieve the CustomProperty value. The value is not shared.

Link to live example(s)

Provide additional details

Context

Useful logs

Thank you for taking the time to report an issue. Our triage team will respond to you in less than 72 hours. Normally, response time is <10 hours Monday through Friday. We do not triage on weekends.

arpitsangwanmsft commented 1 month ago

Hey! Sorry for the delay, we can repro this behavior. We are having internal discussions and will revert back soon.

arpitsangwanmsft commented 1 month ago

Hey @JongHwaPark! As mentioned before, we can repro this behavior and therefore, have added this work item to our backlog. However, at this time, we do not have an estimated timeline for when a fix will be implemented. We appreciate your patience and understanding as we work towards a resolution. Meanwhile, as a workaround you can explore RoamingSettings if it suits your use-case. Internal TrackingID: 344094

JongHwaPark commented 1 month ago

Thanks for the answer, I don't think the Roaming API would be appropriate since storing the information in each mail. Where can I check it using the tracking ID you provided?

neprasad-microsoft commented 2 weeks ago

Hi @JongHwaPark We are working on a fix for this. In the meantime, can you confirm if your manifest has the add-in ID in uppercase or lowercase. In case it is in uppercase, could you change it to lowercase and try again and check if the issue still persists for you?

JongHwaPark commented 2 weeks ago

The ID contains uppercase letters, so I tested it by converting it to lowercase like <Id>1e7e38da7ad6429a9c6f81aa1b9c9344</Id>, but the issue still persists.

neprasad-microsoft commented 2 weeks ago

Hi @JongHwaPark We can reproduce this issue with uppercase ID but not with lowercase. Can you wait for sometime after uninstalling the upper case manifest and check that it was uninstalled and is not available in OWA on page refresh. Then reinstall the manifest with the lower case ID and try again?

JongHwaPark commented 2 weeks ago

I uninstalled the app and confirmed it was removed. Then, I changed the ID field in the manifest.xml to thisistestidinefpinaegpi and reinstalled the app. However, the issue still persists.

neprasad-microsoft commented 2 weeks ago

Hi @JongHwaPark Can you share your manifest? You can share it in a private GH repo. Also, when you say issue still persists, did you try saving a new property, or are you testing with the old property which you had saved previously?

JongHwaPark commented 2 weeks ago

The issue was resolved after changing the ID to lowercase, modifying some properties, and reinstalling. Thank you