Data Quality Services Client Application Error at the matching stage
Hello While creating matching policy with Data Quality Services Client application I have encountered the following error message: As the log says it's related to serialization issue. Deserialization of type System.UnitySerializationHolder, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089 is blocked due to NotInAllow.; w Microsoft.Ssdqs.Studio.ViewModels.Data.Common.Paging.CachedPage`1.WaitForLoad(); w Microsoft.Ssdqs.Studio.ViewModels.Data.Common.Paging.PagedItemsCollection`1.get_Item(Int32 index); w Microsoft.Ssdqs.Studio.ViewModels.Data.Common.Paging.PagedItemsCollection`1.Enumerator.get_Current(); w Microsoft.Ssdqs.Studio.ViewModels.Data.Common.Paging.PagedItemsCollection`1.Enumerator.System.Collections.IEnumerator.get_Current(); w System.Windows.Data.CollectionView.<>c__DisplayClass1_0.<.ctor>b__0(); w MS.Internal.Data.SynchronizationInfo.AccessCollection(IEnumerable collection, Action accessMethod, Boolean writeAccess); w System.Windows.Data.BindingOperations.AccessCollection(IEnumerable collection, Action accessMethod, Boolean writeAccess); w System.Windows.Data.CollectionView..ctor(IEnumerable collection, Int32 moveToFirst); w System.Windows.Data.ListCollectionView..ctor(IList list); w MS.Internal.Data.ViewManager.GetViewRecord(Object collection, CollectionViewSource cvs, Type collectionViewType, Boolean createView, Func`2 GetSourceItem); w MS.Internal.Data.DataBindEngine.GetViewRecord(Object collection, CollectionViewSource key, Type collectionViewType, Boolean createView, Func`2 GetSourceItem); w System.Windows.Data.CollectionViewSource.GetDefaultCollectionView(Object source, Boolean createView, Func`2 GetSourceItem); w System.Windows.Data.CollectionViewSource.GetDefaultCollectionView(Object source, DependencyObject d, Func`2 GetSourceItem); w System.Windows.Controls.ItemCollection.SetItemsSource(IEnumerable value, Func`2 GetSourceItem); w System.Windows.Controls.ItemsControl.OnItemsSourceChanged(DependencyObject d, DependencyPropertyChangedEventArgs e); w System.Windows.DependencyObject.OnPropertyChanged(DependencyPropertyChangedEventArgs e); w System.Windows.FrameworkElement.OnPropertyChanged(DependencyPropertyChangedEventArgs e); w System.Windows.DependencyObject.NotifyPropertyChange(DependencyPropertyChangedEventArgs args); w System.Windows.DependencyObject.UpdateEffectiveValue(EntryIndex entryIndex, DependencyProperty dp, PropertyMetadata metadata, EffectiveValueEntry oldEntry, EffectiveValueEntry& newEntry, Boolean coerceWithDeferredReference, Boolean coerceWithCurrentValue, OperationType operationType); w System.Windows.DependencyObject.SetValueCommon(DependencyProperty dp, Object value, PropertyMetadata metadata, Boolean coerceWithDeferredReference, Boolean coerceWithCurrentValue, OperationType operationType, Boolean isInternal); w System.Windows.Data.BindingOperations.SetBinding(DependencyObject target, DependencyProperty dp, BindingBase binding); w Microsoft.Ssdqs.Studio.Views.Pages.MatchingPolicy.MatchingPolicyRuleView.MatchingRuleResultsColumnsChanged(); w Microsoft.Ssdqs.Studio.Views.Pages.Common.MatchingResultsControl.MatchingRuleResultsColumnsValueChanged(DependencyObject target, DependencyPropertyChangedEventArgs e); w System.Windows.DependencyObject.OnPropertyChanged(DependencyPropertyChangedEventArgs e); w System.Windows.FrameworkElement.OnPropertyChanged(DependencyPropertyChangedEventArgs e); w System.Windows.DependencyObject.NotifyPropertyChange(DependencyPropertyChangedEventArgs args); w System.Windows.DependencyObject.UpdateEffectiveValue(EntryIndex entryIndex, DependencyProperty dp, PropertyMetadata metadata, EffectiveValueEntry oldEntry, EffectiveValueEntry& newEntry, Boolean coerceWithDeferredReference, Boolean coerceWithCurrentValue, OperationType operationType); w System.Windows.DependencyObject.InvalidateProperty(DependencyProperty dp, Boolean preserveCurrentValue); w System.Windows.Data.BindingExpressionBase.Invalidate(Boolean isASubPropertyChange); w System.Windows.Data.BindingExpression.TransferValue(Object newValue, Boolean isASubPropertyChange); w System.Windows.Data.BindingExpression.ScheduleTransfer(Boolean isASubPropertyChange); w MS.Internal.Data.ClrBindingWorker.NewValueAvailable(Boolean dependencySourcesChanged, Boolean initialValue, Boolean isASubPropertyChange); w MS.Internal.Data.PropertyPathWorker.UpdateSourceValueState(Int32 k, ICollectionView collectionView, Object newValue, Boolean isASubPropertyChange); w MS.Internal.Data.ClrBindingWorker.OnSourcePropertyChanged(Object o, String propName); w MS.Internal.Data.PropertyPathWorker.OnPropertyChanged(Object sender, PropertyChangedEventArgs e); w System.Windows.WeakEventManager.ListenerList`1.DeliverEvent(Object sender, EventArgs e, Type managerType); w System.ComponentModel.PropertyChangedEventManager.OnPropertyChanged(Object sender, PropertyChangedEventArgs args); w System.ComponentModel.PropertyChangedEventHandler.Invoke(Object sender, PropertyChangedEventArgs e); w Microsoft.Ssdqs.Studio.Infra.DataObjects.DataObjectBase.InvokePropertyChanged(DataProperty dataProperty, Object oldValue, Object newValue); w Microsoft.Ssdqs.Studio.Infra.DataObjects.DataObjectBase.InternalSetValue(DataProperty dataProperty, Object value, Boolean updateBinding); w Microsoft.Ssdqs.Studio.ViewModels.ViewModels.MatchingPolicy.MatchingRuleEntry.ValueChanged(DataProperty property, Object oldValue, Object newValue); w Microsoft.Ssdqs.Studio.Infra.DataObjects.DataObjectBase.InvokePropertyChanged(DataProperty dataProperty, Object oldValue, Object newValue); w Microsoft.Ssdqs.Studio.Infra.DataObjects.DataObjectBase.InternalSetValue(DataProperty dataProperty, Object value, Boolean updateBinding); w Microsoft.Ssdqs.Studio.ViewModels.ViewModels.MatchingPolicy.MatchingRuleEntry.LoadResults(); w Microsoft.Ssdqs.Studio.ViewModels.ViewModels.MatchingPolicy.MatchingPolicyMatchingRulesViewModel.AnalyzeResults(); w Microsoft.Ssdqs.Studio.ViewModels.ViewModels.Common.ProcessExecuterViewModel.UpdateState(ProcessData data); But I don't know what does NotInallow mean Could you please help?
Does anyone inform their users how to set OneDrive to open in the client applications?
I'm looking for other opinions and experiences on this because of a question I've been asked. There are two ways to change your OneDrive for Business area (in browser) to open documents in the client application. It only affects the OneDrive that it is being set upon though, but it definitely has ripple effects that can cause confusion in users when they experience inconsistencies in behaviors. I think the shared documents experiences in particular might be the areas that would experience most of the weird behaviors. Has anyone else documented or instructed users about doing this? What behavior changes in the UI were noticed by people? Was it confusing or did people just brush off the inconsistent opening in the browser/client application experiences?
