Skip to main content
Question

Report Studio .REP Layout - Customer Solution Repository

  • April 28, 2026
  • 2 replies
  • 23 views
T
Superhero (Partner)
Forum|alt.badge.img+14

Should I assume that the .REP layout files, that are created in Report Studio, are to be placed into the customer’s solution repository, just like any other layout that is created? I don’t see any guidance in the tech docs on this process - other than the idea of export/import between instances.

Does IFS have anything indicating best-practice for the new Report Studio layouts?  Should we advise our clients to follow the same practice as when a new RDL layout is created ie: put it in the proper server/reports/layouts folder and PR it into the customer solution master?  

 

2 replies

ashen_malaka_ranasinghe
Hero (Employee)
Forum|alt.badge.img+14

Hi ​@Tracy Norwillo,

There is currently no official IFS guidance confirming that Report Studio (.REP) layouts should be handled the same way as traditional RDL layouts in terms of filesystem placement or solution repository delivery.

Report Studio introduces a shift towards a web based, configuration driven model where layouts are created, stored, and versioned within IFS Cloud itself, with export/import being the documented mechanism for moving layouts across environments.

As such, while retaining REP files in a repository for version control is a good governance practice, they should not be treated as deployment artifacts in the same way as RDL layouts (i.e., placing them under server/report/layouts or relying on PR based delivery).

Find me on LinkedIn as Ashen Malaka: https://www.linkedin.com/in/ashen-malaka-ranasinghe/
T
Superhero (Partner)
Forum|alt.badge.img+14
  • Tracy Norwillo
  • Author
  • Superhero (Partner)
  • May 12, 2026

​@ashen_malaka_ranasinghe 

After I asked the question, I did some more research in the tech docs and found the general guidance to commit configurations to the Customer Repository for “safe keeping”.  This aligns with your last paragraph.

https://docs.ifs.com/techdocs/ale/020_lifecycle/035_configuration_management/#overview

Can you explain more about not treating them like RDL layouts by placing them in the same  server/report/layouts location?  Where should they be placed?  I took a look at where the Core layouts are delivered and they are in the same layouts folder.

 

    Terms & ConditionsAccessibility statement