Skip to main content

Dear Team,

Can anyone tell me Is there any possibility to display the attachment in reports.

We are trying below steps for displaying the attachments in reports

  1. Adding the Customer Signature for a task in mobile.

  2. In Report adding Image control, setting the Image source as 'External' in the properties.

  3. Fetching attachment path of the signature in query and configuring that in the image.

  4. Then uploading the RDLC file in the FSM application and generating the report, but attachment is not coming in the report.

  5. We have given the attachment directory app param.

 

 

Hi @TatKkkkkR ,

I assume that your environment is hosted in managed cloud. Hence, even though you have provided the attachment path to the blob storage it won’t directly allow you  to the access the stored attachments externally. In order to make this work, you will need to request for a SAS (shared access signature) token key to Azure storage. When you open up the cloud-ops request, (if the hosted environment belongs to ifs cloud) make sure to provide a reasonable validity period for the token just to make sure that it will not expire soon.

Once you received the sas token key, you need to simply append the key at the end of your attachment path url, similar to the example below. You can test whether the attachment is displayed in your browser itself by browsing through the same link.

https://yourblogstorage.blob.core.windows.net/attachments/image_id01.png?the_sas_token_key_value

Then the same attachment path with SAS token key should be added to your rdlc query so that it should correctly display the image on your report.

Thank you

Dear Team,

Like suggested, we are trying to open the image file through browser using the token key, but not getting the image.
Please help us to browse the image.

 

The link we are trying to open by using the token key at the end - https://gilbfsmdevstorage.blob.core.windows.net/attachments/task_SOMOGVR_119_20221013114232.jpg?sv=2021-06-08&ss=f&srt=sco&sp=rwdlc&se=2024-11-03T13:06:07Z&st=2022-11-03T05:06:07Z&spr=https&sig=GH6a9S7aK%2BLtCLoOI2eLNquytt2VhFVokK9hqS6Qv3g%3D

 

 

Thank you

Did you already check the ATTACHMENT_DIRECTORY app param whether it has been updated with the blob URL? https://gilbfsmdevstorage.blob.core.windows.net/attachments

Otherwise, you may need to check the SAS token key validity with the cloud ops team.

 

Reply


Terms & ConditionsCookie settings