You’re offline. This is a read only version of the page.
50
I have customized my CRM account navigation to include a link to our ISV application which I would like to be display in the detail area of the Account page (which as far as I know is an IFRAME).
Now everything works fine when I am linking to the application running in Visual Studio but when I deploy the application to a IIS server in our QA environment - the link to our ISV application shows the page in a top level window and the account detail page is no longer seen.
Given that it works in Visual Studio I am lead to believe that it is not the application itself but something in the deploying it to IIS that is causing the problem
Any ideas???
Whatty
*This post is locked for comments
I have the same question (0)
Whatty,
As long as you deployed your solution to either the ISV folder within the CRM website or on a custom IIS site that you are referencing in your IFRAME via the URL, it should be fine from a deployment perspective.
Where I've seen this happen before is if the ISV Application, tries to start as a new application or is dependent upon some additional windows. I ran into this with a Java Web App that we were trying to display in an IFrame. When the IFrame would load the Web Application would try to initialize and it ended up re-directing the parent window (CRM Record) to the URL of the Java Web App itself.
We had to move the ISV integration out of the IFRAME and into a button on the Toolbar and open it in a new window. We only did this because there wasn't enough time in the course of the project to re-write and re-engineer the application since we were only using 2 specific pages within the app.
Thanks,
Jeremy Winchell
Inetium
Share
Report
All responses (
Answers (
