Since updating to the latest version of Windows Outlook I can no longer see the message created by Office.context.mailbox.item.notificationMessages.replaceAsync. In a previous version (can't recall which) it was visible:
In the latest version of Outlook I can see a busy indicator and the text "... Add-in is working on your ... request" but then that disappears but the notification message does not appear.
Edit: This is for Version 1908 (Build 11929.20254 Click-to-Run)
Related
I have an Add-in I have written for Microsoft Outlook. The Add-in runs in a task pane. I have a button on the html in the page that opens a new window using Office.context.ui.displayDialogAsync. This button works fine in the web client, but when clicked in the full Outlook client, a window appears and disappears in a split second. This Add-in was developed outside VS so not sure how I can debug apart from in web client, which not does have the issue.
The domain is the same, and the domain is in the appDomain of the XML manifest. The URL is also https.
Does anyone have any ideas, have I missed something that says this isn't available in full client and only available in web client?
About Outlook version:
Version 2102 (Build 13801.21004 Click-to-Run)
Microsoft Office for Outlook 365 MSO (16.0.13801.21002) 64-bit
If I clock Office Updates, it tells me Office is up to date.
Update
I have another machine with Outlook installed, and I have discovered the dialog opens fine on the full outlook client. Looking at the version for that version of outlook (logged in to the same Office 365 account), the version shows as:
Version 2110 (Build 14527.20226 Click-to Run)
Microsoft Office for Outlook 365 MSO (Version 2110 Build 16.0.14527.20168) 64-bit
So it looks like maybe the earlier build had an issue in Outlook?
Would you like to share a screen recording in the machine where the API is not working?
Besides, you could also try a test add-in with this: Manifest.
It's an app command so you can click "Show Taskpane" first, and then click "launchDialogSameOrigin" button in the taskpane. You can observe whether the dialog is working correctly in this add-in.
Thanks.
I work on an add-in for Microsoft Outlook, and recently we’ve received reports from some users that they can no longer click on buttons in the taskpanes of add-ins. Other add-ins, not just ours, have been affected by this issue. Affected users can still open the taskpane without issue. Our taskpane web view loads correctly, but then any clicking inside the taskpane has no effect. We are not seeing console errors when this happens.
To help narrow things down further: we’ve seen this issue occur in Outlook 2019 and Outlook for Microsoft 365 MSO with Office 365 accounts so far. We’ve seen this issue happen when the taskpane is opened from Compose view. One affected user was using Outlook 2019 version 16.0.13127.20266 (32-bit). Affected users have been running Windows 10, version 2004. A team member was able to reproduce the bug by updating to version 2004, but the bug disappeared for them after a subsequent system update on the same version 2004.
Has there been any recent change to add-in taskpane behavior that could be causing this issue?
This issue was fixed, and the fix should be available in Windows build 19043.1266 or later. Note that it is the Windows Build that matters, not the Office build.
We are seeing the same thing since updating to Windows 10 build 2004. For us, the add-in task pane freezes when the user tries to reply to an email (which is also compose view I guess).
Would be good to get an update on this as it is breaking the add-in for our users.
We are using Outlook Version 2009 (Build 13231.20200)
This is Outlook for Microsoft Office 365 MSO (16.0.13231.20146) 64 bit.
I've submitted my outlook add-in 6 times now and every time the certification failed for a different reason. The last rejection reason I got was that my add-in didn't work on Office 2013 and Office 2016 (which they also refer to as O365 Perpetual).
I develop on a Mac and I have no idea how to go about debugging why my add-in is not working on those older Offices. Can't I just drop support for older Office suites? How could I test these environments?
I'm pretty close to quitting and just not publishing my outlook addin. I have never experienced a worse app review process.
If you want to be published on the Office Store, you need to support all the platforms for the minimum Outlook API Requirement Set in your manifest.
If you do not need to support Outlook 2013 or Outlook 2016, you can set your minimum API requirement set to 1.5, which will drop support for those versions (1.4 was the last version supported by those versions of Outlook). When you submit to the Office Store, please make a note that your minimum API set means that the add-in will not run in those Office clients.
We're developing and Outlook web add-in that needs requirement set 1.4, which is supported by both Outlook 2016 CTR and MSI.
We have Outlook 2016 MSI 64-bit installed on 2 different machines. Machine A has Outlook installed long ago and it has windows auto update turned on. Machine B has just had Outlook installed today without any update.
When we tested the add-in on both machine, it's loaded into Outlook of A, but not B. We figured out that Outlook on A is the latest version but Outlook on B is not, so we tried to trigger Windows update on B manually, but it cannot find any update for Outlook. We then tried to download and install the latest update for Outlook from this site, but the result is not as expected:
OUTLOOK.EXE is updated to 16.0.4732.1000, which is the same with
machine A
Outlook > File > Office Account > About Outlook still shows:
16.0.4266.1001, which is different from machine A: 16.0.4639.1000
Requirement Set is updated to 1.3, not 1.4 (we used F12Chooser to
check)
Is there any wrong with our update process? How can we have Outlook on B fully updated just like on machine A?
We recommend getting updates through Microsoft Update since it will update all of the right files.
In your specific case, for Outlook 2016, try also installing this update, which is needed for requirement set 1.4.
Is it possible to change the font colour in the Note activity CRM 2016? Mine is white so users do not see what they are typing.
There is a bug in older versions of CRM where the notes text cannot be seen in newer versions of Chrome and Firefox.
Have you already updated to the latest updated of CRM 2016? I am fairly certain that it has already been fixed by Microsoft, even though I was unable to spot the fix in the release notes. For comparison this was fixed for CRM 2015 in Update 0.3, released in August 2017 (Unable to view notes fields after updating to Mozilla Firefox version 49.0.1).
If you are unable to upgrade to the latest version, the following unsupported fix can be used. From the Dynamics Community:
In Program Files\Microsoft Dynamics
CRM\CRMWeb_static\css\1033\notesv2.css change line #118 to color: #000000;
Replace 1033 with the LCID of the language(s) your users are using.
The technical explanation of what changed in Chrome and Firefox can be seen here: CRM 2016 and Firefox 49 issue with notes.