Can someone tell me how to migrate a hmtl composer generated htm file (that creates a coordinated active reports) to MRE for users to run? I tried 'export as procedure' and migrated that fex. It did not work (got a http 500 error). I tried to create a launch fex with -HTMLFORM and that did not work too well.
Thanks in advance.

The resultant page (created in MRE) should be "something.htm". If so, just run it.

Where did you develop it? In Projects? In an App Folder? You should be able to drag it into an MRE Domain Standard Report folder...

I developed that in local project in STUDIO. Putting the html file as is into MRE Standard Reports is no good because when you run it, you got multiple browser window opened, one with 'NO query info to decode' error and the other does show the html page but nothing populated.

I never use Projects (can't see the use for them) and I usually don't develop locally if the final destination is the server. If you're working with MRE, create a domain for yourself on the server that the report is supposed to run on.

I don't know why you get two windows opened. You have an html page with nothing populated most likely because the html page calls fexes that are not where they're supposed to be or where they're coded to be - verify domain names, folder names and fex names in the html code.

we develop it in local project because as developers, we need to follow migration procedure. We develop on local desktop, then move/migrate to test server, then to QA and eventually prod servers.

I got multiple windows because, I believe, it got multiple reports in the html file. Of course, as I said, it should not do that.

Well, it's not going to be easy to migrate code from a local project to a remote MRE - MRE launch pages require MRE parameters to be passed to a called fex.

I would not use the Projects area st all.

You have four environments for reporting? I think that's quite excessive.

I would develop in the MRE environment of the Test server, then migrate to QA, then to Prod, making sure Domain names, Folder names and Fex names are exactly the same on all servers.

thanks, Francis. Actually, we have more than 4 envs. That is why I thought the 'Export as Procedure' is the option provided for the migration purpose. Of course, that did not work.