microsoft / Dynamics365-Apps-Samples

Sample code for Dynamics 365 apps
https://docs.microsoft.com/dynamics365/
MIT License
149 stars 223 forks source link

Smart Assit Adaptive Card icons in Productivity pane not displaying #22

Open MTH2019 opened 4 years ago

MTH2019 commented 4 years ago

I have implemented the Smart Assist bot in our Omni-channel instance. It is working fine except for the Icons in the cards. When the cards is displayed in the Productivity Pane, the icons are being prefaced with "https://urlp.asm.skype.com/v1/url/content?url=".

I have tried using both the Icon data that was originally in the Smart Assist solution and also a webresource in D365 CE. OpenIcon = "data:image/png;base64,iVBORw0KGgo..." webresource = "https:///WebResources/msdyn_/Images/openicon.png"

I believe the icons were working when we exposed Smart Assist in a section on the Conversation Summary form. This started after moving it to the Productivity Pane.

susikka commented 4 years ago

@Har1pr1ya can you please take a look at this issue?

susikka commented 4 years ago

@MTH2019 This is a known issue that images are not showing up in certain browsers. Developers are working with the relevant teams on fixing this issue. Please stand by till further info on this.

MTH2019 commented 4 years ago

Any word on this yet? Really hindering our development of the Smart Bot. The buttons also do NOT render correctly as they do in the emulator. They are laid out horizontally with no borders. More than 2 buttons and they fall off the card.

respiridion commented 4 years ago

@susikka Any update on this issue ? we are currently doing some development and this issue became a road block.

we got some issue on the rendering of the image.

image

when we are passing image to the button. its giving us :

Authorization has been denied for this request.

image source parsed to : https://urlp.asm.skype.com/v1/url/content?url=https%3a%2f%2f *****.core.windows.net%2fginasset%2fSampleIcons%2frobot2.png

susikka commented 4 years ago

@respiridion @MTH2019 The feature team is actively working on resolving this issue and hopefully the fix will be available soon.