Using QuickForms in Web Browser Controls in a Dialog in the Infor CRM (Saleslogix) Web Client

Kris wrote previously about a change you can make to allow using QuickForms in Web Browser controls. That change is a necessary one to make, however, there is one more change you must make if you’ll be using QuickForms in the Web Browser control that you will be showing as a dialog. When the form is shown in the dialog workspace, there is a problem that prevents the QuickForm in the Web Browser control from getting it’s data context, so the controls are essentially unbound. You won’t see any data in the controls and any data you enter won’t be saved. This can be fixed in a similar way to what Kris outlined in the article I linked to above. What Kris outlined in that article must be done as well as the steps I’ll outline below.

First, make sure you’ve done the steps in Kris’ article Allowing quickforms to be used within the Web Browser control in the web client

Once you’ve done those steps, you must do a similar change for the QFBrowserControl.WebControlRenderingTemplate.vm. To do this, perform the following steps:

In the Application Architect, in the Virtual File System Explorer (Control + Alt + F), expand out Model…Quickforms…Web

 

Locate the file QFBrowserControl.WebControlRenderingTemplate.vm. Double click this file.

 

Look for the following line (in 8.3 this is line number 13):

sp.DialogService = DialogService;

 

Change that to be (all on one line):

if (DialogService != null) sp.DialogService = DialogService;

 

Now, look for the following line (in 8.3 this is line number 17):

esp.InitEntityBoundSmartPart(PageWorkItem.Services.Get(<Sage.Platform.Application.IEntityContextService>));

 

Change that to be (all on one line):

esp.InitEntityBoundSmartPart(this.EntityContext ?? PageWorkItem.Services.Get<Sage.Platform.Application.IEntityContextService>());

 

Then save the changes to the file.

Now when you build and deploy you will be able to place quickforms within the web browser control and it should work fine whether or not it is in a dialog.

Important:

You must close and reopen Application Architect after making this change. Then, do a full rebuild by going to the “Build” menu and select “Rebuild Web Platform” (or hold the Control/CTRL key while clicking the Build Web Platform button on the toolbar).

Also, if you’re using an exported VFS on the file system, you need to change this in the exported model. Navigate to the directory where your model exists and locate the files to change there. The Virtual File System Explorer area in Application Architect is only looking at the files in the database, not in the exported model. If you’re using the VFS in the database, the files in the Virtual File System Explorer are the correct ones to change, but not for an exported VFS in the file system.