Loading...
меню

Archives

Unable activate Quest Web Parts feature in Site Settings: “Requested registry access is not allow

Unable activate Quest Web Parts feature in Site Settings. Seeing the follwoing error in ULS logs:
Feature receiver assembly ‘QuestWebPartsFeature, Version=1.0.0.0, Culture=neutral, PublicKeyToken=2b4b09f1c57c8f0b’, class ‘Quest.WebParts.Feature.FeatureReceiver’, method ‘FeatureActivated’ for feature ‘11730bed-af16-4fd0-985b-3ffa4792928f’ threw an exception: System.TypeInitializationException: The type initializer for ‘Quest.WebParts.Feature.FeatureLogger’ threw an exception. —> System.Security.SecurityException: Requested registry access is not allowed. at Microsoft.Win32.RegistryKey.OpenSubKey(String name, Boolean writable) at System.Diagnostics.EventLog.GetEventLogRegKey(String machine, Boolean writable) at System.Diagnostics.EventLog.Delete(String logName, String machineName) at Quest.WebParts.Feature.FeatureLogger..cctor() The Zone of the assembly that failed was: MyComputer — End of inner exception stack trace — at Quest.WebParts.Feature.FeatureLogger.Error(String message) at Quest.WebParts.Feature.FeatureReceiver.FeatureActivated(SPFeatureReceiverProperties properties) at Microsoft.SharePoint.SPFeature.DoActivationCallout(Boolean fActivate, Boolean fForce) fffc4665-415f-4b83-a7bd-33ecc976d545

Duplicate Entry in Version History

After creating a new item in any Discussion list via qListForm an extra version is added. This happens only when creating an item that contains Enhanced Richtext field.
 

Custom Actions Examples.

The Custom Action capability enables you to write a custom code that can be called from qListView, qListForm, qSIListView or qSIListForm Web Parts. In your custom code, you can virtually do anything you want with the data. For example:
• You can write a complex custom validation and abort the action if the data is invalid.

• You can copy the item to another list or library before the item is saved in a qListForm.

• You can initialize one or more fields in the qListForm when the list form is initialized. Please see the Form Initialization Actions property of the qListForm and qSIListForm on how to call this kind of custom action. Please also see the code example below on how to write a custom action to initialize the list form.

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.

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.