Configure logos and conditional branding in IFS reports

Explore this learning path

Documentation-based guide draft · Reviewed against sources on 2026-09-27 · Not executed in an IFS environment. IFS references use 26R1 unless stated otherwise. Confirm available APIs, components, and permissions in your installed release.

Add a company logo to an IFS Report Designer layout, make it available at runtime, and verify the correct logo for two companies. The key distinction is that a local preview image does not automatically upload the image used by the server.

Before you start

Use a development Report Designer layout, its matching schema, permission to import layouts and Report Images, and two fictional company test cases. Save the current RDL and image exports before editing. This procedure is for Report Designer; Report Studio has a different image configuration.

Prepare a small PNG/GIF/JPEG with its pixels already oriented correctly. Report Designer does not apply EXIF rotation as an image editor would.

1. Find the layout actually selected at runtime

Order the report and record the Report ID, selected layout, language, and company. Open Report Definitions and inspect that report’s registered layouts and default layout type. Export the selected layout.

Do not edit a similarly named RDL that is not registered for the report. Keep a baseline PDF for later comparison.

2. Add the local image reference

1. Open the exported layout in Report Designer.
2. Under Edit → Options, set the graphics path to your lab graphics folder.
3. In the schema tree’s Graphics area, use Add graphics to select your logo.
4. Drag the image onto the layout’s header area.
5. Select the image and enable Keep aspect ratio.
6. Select Standard Images or Logos and enable Default logotype support for the company-logo behavior.

For a common default logo, use the documented complogo.gif setup in the standard-logo directory. Preserve the actual format; do not rename a PNG extension to GIF without converting the image.

3. Upload the runtime image

Open Report Images in IFS, select the Logos tab, and import the matching file. Confirm the filename and preview. A static report-specific decoration instead belongs in the Images tab with the required module/report information.

Consider Prevent Overwrite for an intentionally maintained custom image, following your release process. Record that setting so a later delivery does not silently replace your choice.

4. Register and import the layout

In the report definition’s layout list, use a unique lab layout title. Ensure its layout name and type match the RDL. Use Import Layout for the layout row and import a matching schema only when the report definition requires one.

Generate a new report and explicitly select the lab layout. Confirm the logo appears in the runtime PDF, not just in the designer preview. If the old logo remains, first check the selected layout and image identifier before changing global defaults.

5. Add company-dependent selection

The documented default-logo logic checks the archive variable rhSysLogo before falling back to the default logo. For an existing report that already supplies it:

1. Generate a report for company A and inspect its archive variables through the available report administration tools.
2. Record the rhSysLogo value and confirm that image exists in Report Images.
3. Repeat for company B.
4. Keep Default logotype support enabled on the layout image so it consumes that value.

If the report does not supply the variable, use an approved report customization to set it from the report’s company context, or a Set Archive Property rule scoped to this report. In that rule, use Get Expression to select the company field from the report XML and set the appropriate archive variable. The documented archive-variable format is:

rhSysLogo:YOUR_REGISTERED_LOGO_REFERENCE:S

Use a reference proven by the report/image configuration; do not assume a local file path is a server image URL. Create mutually exclusive conditions for the two companies and inspect the resulting archive variable before testing the image.

6. Check the fallback and roll back

Test company A, company B, and a record without a company-specific override. Check proportions, print quality, page breaks, and the intended fallback logo. An incorrect company logo is a data-selection defect, even when the image renders perfectly.

Symptom	Likely check
Preview works, runtime missing	Image was not imported or runtime identifier differs
All companies use one logo	Missing/constant rhSysLogo or disabled default-logo support
Distorted logo	Aspect-ratio setting/container dimensions
Correct image disappears after delivery	Image overwrite policy and import process

Restore the exported layout and disable any lab rule to roll back. Remove only images created for this exercise after confirming no other layout uses them.

See Report Images administration for import/export and overwrite behavior.

Sources and scope

• IFS Report Designer image handling

Older IFS Applications examples are historical context, not evidence of Cloud compatibility. No third-party code, screenshots, or downloadable workflows are reproduced.