Skip to content
Loading...

Archives

Cross Site Look up field format for DropDown

Cross Site Look up field format for DropDown

List has a lookup field that is linked to a cross-site lookup field. In the dropdown, values from cross-site lookup are not coming in proper format.

Does Quest webparts support Custom fields?

Does Quest webparts support Custom fields?

We have a custom field created in SharePoint. Native SharePoint method is overwritten for that field and the field is getting updated when OOB form is used to create an item. When we save a new item using qListForm web part, a value of the field is not populated.

Multiple sort fields in qSelector.

Multiple sort fields in qSelector.

I have been using a qSelector to present some data for the user and I need to be able to sort data in the dropdown by 2 different fields: by Category first then by Title.

Enhancement: Values migrated by NMSP should be converted to cross-site lookup

Enhancement: Values migrated by NMSP should be converted to cross-site lookup

Some items were migrated from Lotus Notes with NMSP, and NMSP creates values in the “cross-site lookup” field as a regular single line of text.

But if you use qListView to display cross-site lookups, values for items migrated from Notes are blank.

Web part management pages

Web part management pages

Sometimes Quest Web Parts section is not available on SharePoint Central Administration.