[Anonymous]

Hello,

n

n

  I tried to reproduce your scenario using QuickApps 6.3 for SharePoint 2010 and it worked well for me. The 2nd dialog refreshed and the dialog window size hasn't changed.

n

See below:

n

I have a qListView wp to display some data and I edit an item in a dialog using a qListForm (Students – Mr) . On this dialog I have a custom action that opens a 2nd dialog (Case2482715Page) when I added a qLisTForm that has a lookup field (Continent) that refreshes the page when the selection changes. I see the form refreshing just fine, no change in the window size.

n

Please confirm that I got right your scenario.

n

Thanks,

n

n

PS

n

What are the QA and SP versions you use?

n

[Anonymous]

Hi olae, you have a similar set up to what I'm doing however there's a slight difference on how the module dialogues open up.

n

I have some jquery which calls:

n

SP.UI.ModalDialog.commonModalDialogOpen(dURL, options, CloseDialogCallback, null);

n

Our SharePoint version is 14.0.0.6117

[Anonymous]

Hello,

n

  In my env.I don't have any customization but ezEdit only.

n

Can you remove your custom code and see how that goes?

n

Thanks,

n

n

  

[Anonymous]

Hello, I currently have a setup where the user is presented a list of information and they are able to click on an item which brings up the details in a dialogue window.  If I have a qSelector here it refreshes the dialogue window without problem.  However I have an option for the user which opens a second dialogue window where they have a choice using the qSelector webpart.

n

The qSelector webpart is sending values to a qListView and a qListForm (via a session).  In order for the qListForm to have updated values I need to refresh the page, however using the built-in refresh option with the qSelector webpart causes unwanted behaviour.  Instead of the dialogue window refreshing, the dialogue is refreshed in full screen.

n

Is that the expected behaviour?  I currently have a few possible solutions which will use custom jquery to refresh/etc. but I’d like to avoid that if possible.

[Anonymous]

I'm unable to remove the custom code.  The same situation works for other pages however.

n

I did write a small work-around though.

n

I linked the dropdown to a ListView and then I have some custom jscript which parses the appropriate values and links them together in a function:

n

// SID1: SharePoint ID for first item.
// SID2: SharePoint ID for second item.
// field1: SharePoint field name for first item.
// field2: SharePoint field name for second item.
// list: The list where the two values will be linked
function linkIDs(context, SID1, field1, SID2, field2, list) {

n

console.info("linkIDs:\n\tSID1: %s\n\tSID2 %s\n\tfield1: %s\n\tfield2: %s\n\tlist: %s", SID1, SID2, field1, field2, list);

var clientContext = context;

n

var oList = clientContext.get_web().get_lists().getByTitle(list);
var item = new SP.ListItemCreationInformation();
var oListItem = oList.addItem(item);

n

var Item1LookupField = new SP.FieldLookupValue();
var Item2LookupField = new SP.FieldLookupValue();

n

Item1LookupField.set_lookupId(SID1);
oListItem.set_item(field1, Item1LookupField);

n

Item2LookupField.set_lookupId(SID2);
oListItem.set_item(field2, Item2LookupField);

n

oListItem.update();

n

clientContext.load(oListItem);

n

return clientContext;
};

[Author]

Posts