• Replies 4 replies
  • Subscribers 338 subscribers
  • Views 185 views
  • Users 0 members are here
Related

Infomaker: photo in constituent header

Martin Keen (Past Member)
$organization

Folks,

I'm using Infomaker for the first time in this working environment - we're hosted in RAMP.  I'm using IM rather than SSRS as it's for a custom header.  I'm sure it's an easily remedied problem but can't find a solution elsewhere so asking here!

For a limited number of constituents, I would like to be able to put their picture in the header but don't appear to be able to get the specification right/file path right.  Ideally, this would be  controlled by a string that includes the customer_no value ("L:\images\"+string(customer_no)+".JPG").  I'm having problems getting this to work.

If I use the explorer to select an image the File Name field is completed with L:\images\262483.JPG the image is displayed in the design pane but does not show in the preview pane.  if I use the string containing the customer_no, no picture is displayed in either pane.  

It's been a LONG time since I tried this - I've done it before and know it's possible - does anyone have any sage advice about how to do this successfully please?  Does the image object need a specific name?

Martin 



[edited by: Martin Keen at 9:57 PM (GMT -6) on 15 Jan 2017]
Parents
  • $organization
    Hi Martin, Just a couple of recommendations from my experience creating a custom header with Constituent images. » All photos should be in bitmap (.BMP) format. » Resize the images to approx. 200 x 200 pixels in size. » Use the constituent number as the name of their profile image (eg. 123456.BMP). » Load the images in a folder structure that is accessible to SQL Server If using the RAMP User Desktop, the path we use is as follows. eg. L:\Documentation\Constituent_Images\ NOTE: This is not the path reference you should be using in your stored procedure; this is the path reference for the RAMP User Desktop only. » Your stored procedure should reference the entire path and filename for the constituent image. In our case, the field in the stored procedure is as follows... const_img = '\\kriostess\pub\[YOUR DATABASE NAME HERE]\LIVE\Documentation\Constituent_Images\' + CAST(@customer_no AS VARCHAR) + '.bmp' » In your stored procedure, it's important that you don't use a mapped drive reference to link your image; instead use the full URL as shown above. » In your InfoMaker report, ensure the the image properties have the 'Display as Picture' and 'Visible' options selected/checked. Also ensure the size the field/image on the report is large enough to display the entire image. You can make it larger than necessary for testing and then reduce it to fit properly in the header. » Keep in mind that the header has a specific height requirement. Creating a header in InfoMaker that is too tall will not display correctly in Tessitura. In our custom Constituent header, the Constituent images are 251w x 224h. With the header itself being approx. 250 in height. » In addition to the Constituent image itself, add a text box below the image that displays just the path & filename of the image (value returned from the stored procedure). This way you can determine if the image is not being displayed or if the filename is not correct for the associated image. » Preview the report in InfoMaker before you launch in Tessitura. Hope this helps. Cheers, Brad


    [edited by: Brad Staples at 9:57 AM (GMT -6) on 20 Jan 2017]
Reply
  • $organization
    Hi Martin, Just a couple of recommendations from my experience creating a custom header with Constituent images. » All photos should be in bitmap (.BMP) format. » Resize the images to approx. 200 x 200 pixels in size. » Use the constituent number as the name of their profile image (eg. 123456.BMP). » Load the images in a folder structure that is accessible to SQL Server If using the RAMP User Desktop, the path we use is as follows. eg. L:\Documentation\Constituent_Images\ NOTE: This is not the path reference you should be using in your stored procedure; this is the path reference for the RAMP User Desktop only. » Your stored procedure should reference the entire path and filename for the constituent image. In our case, the field in the stored procedure is as follows... const_img = '\\kriostess\pub\[YOUR DATABASE NAME HERE]\LIVE\Documentation\Constituent_Images\' + CAST(@customer_no AS VARCHAR) + '.bmp' » In your stored procedure, it's important that you don't use a mapped drive reference to link your image; instead use the full URL as shown above. » In your InfoMaker report, ensure the the image properties have the 'Display as Picture' and 'Visible' options selected/checked. Also ensure the size the field/image on the report is large enough to display the entire image. You can make it larger than necessary for testing and then reduce it to fit properly in the header. » Keep in mind that the header has a specific height requirement. Creating a header in InfoMaker that is too tall will not display correctly in Tessitura. In our custom Constituent header, the Constituent images are 251w x 224h. With the header itself being approx. 250 in height. » In addition to the Constituent image itself, add a text box below the image that displays just the path & filename of the image (value returned from the stored procedure). This way you can determine if the image is not being displayed or if the filename is not correct for the associated image. » Preview the report in InfoMaker before you launch in Tessitura. Hope this helps. Cheers, Brad


    [edited by: Brad Staples at 9:57 AM (GMT -6) on 20 Jan 2017]
Children