2017-07-04 47 views
2

Dynamics CRM 365默認情況下僅在實體窗體的註釋塊上演示有限數量的註釋。在我的情況下,它是10個音符。當用戶滾動記錄時,剩下的筆記應該是'延遲加載'。不知怎的,這個功能被打破了,筆記沒有加載。CRM:在窗體上顯示所有註釋而不是延遲加載

enter image description here

沒有什麼有趣的既不在控制檯,也沒有在服務器的事件日誌。這是完全的怪病。

是否有任何選項可以同時裝載所有紙幣,如在舊的CRM 2011中一樣?

或者,也許任何人都可以建議如何調查此問題?


UPDATE: 剛纔檢查這一問題上的「警告」級別追蹤工具,這裏就是它表明,當我嘗試加載註釋:

[2017-07-06 08:39:43.344] Process: w3wp |Organization:00000000-0000-0000-0000-000000000000 |Thread: 39 |Category: Exception |User: 00000000-0000-0000-0000-000000000000 |Level: Error |ReqId: 055f8ace-5e77-4c01-b980-0e97088ed4aa |ActivityId: 055f8ace-5e77-4c01-b980-0e97088ed4aa | CrmHttpException..ctor ilOffset = 0x22 
    at CrmHttpException..ctor(HttpStatusCode statusCode, String message, Object[] args) ilOffset = 0x22 
    at CrmODataOptimisticConcurrencyHelper.HandleGetMatchETags(CrmODataExecutionContext context, Entity entity) ilOffset = 0x129 
    at CrmODataServiceDataProvider.RetrieveEntityWithRelatedRecords(CrmODataExecutionContext context, EntityReference primaryEntityReference, QueryExpression qe, RelationshipQueryCollection relatedEntitiesQuery) ilOffset = 0x19 
    at CrmODataServiceDataProvider.RetrieveEdmEntity(CrmODataExecutionContext context, String edmEntityName, String entityKeyValue, ODataQueryOptions queryOptions) ilOffset = 0x2D 
    at EntityController.GetEntity(String entityName, String key) ilOffset = 0x32 
    at ilOffset = 0xFFFFFFFF 
    at <>c__DisplayClass10.<GetExecutor>b__9(Object instance, Object[] methodParameters) ilOffset = 0x0 
    at ReflectedHttpActionDescriptor.ExecuteAsync(HttpControllerContext controllerContext, IDictionary`2 arguments, CancellationToken cancellationToken) ilOffset = 0x34 
    at <InvokeActionAsyncCore>d__0.MoveNext() ilOffset = 0x52 
    at AsyncTaskMethodBuilder`1.Start(TStateMachine& stateMachine) ilOffset = 0x2C 
    at ApiControllerActionInvoker.InvokeActionAsyncCore(HttpActionContext actionContext, CancellationToken cancellationToken) ilOffset = 0x35 
    at ApiControllerActionInvoker.InvokeActionAsync(HttpActionContext actionContext, CancellationToken cancellationToken) ilOffset = 0x3 
    at <ExecuteAsync>d__2.MoveNext() ilOffset = 0xD9 
    at AsyncTaskMethodBuilder`1.Start(TStateMachine& stateMachine) ilOffset = 0x2C 
    at ActionFilterResult.ExecuteAsync(CancellationToken cancellationToken) ilOffset = 0x35 
    at ApiController.ExecuteAsync(HttpControllerContext controllerContext, CancellationToken cancellationToken) ilOffset = 0x138 
    at <SendAsync>d__1.MoveNext() ilOffset = 0x123 
    at AsyncTaskMethodBuilder`1.Start(TStateMachine& stateMachine) ilOffset = 0x2C 
    at HttpControllerDispatcher.SendAsync(HttpRequestMessage request, CancellationToken cancellationToken) ilOffset = 0x3D 
    at HttpMessageInvoker.SendAsync(HttpRequestMessage request, CancellationToken cancellationToken) ilOffset = 0x3C 
    at HttpRoutingDispatcher.SendAsync(HttpRequestMessage request, CancellationToken cancellationToken) ilOffset = 0xBF 
    at DelegatingHandler.SendAsync(HttpRequestMessage request, CancellationToken cancellationToken) ilOffset = 0x19 
    at <SendAsync>d__0.MoveNext() ilOffset = 0x17D 
    at AsyncTaskMethodBuilder`1.Start(TStateMachine& stateMachine) ilOffset = 0x2C 
    at CorsMessageHandler.SendAsync(HttpRequestMessage request, CancellationToken cancellationToken) ilOffset = 0x3D 
    at DelegatingHandler.SendAsync(HttpRequestMessage request, CancellationToken cancellationToken) ilOffset = 0x19 
    at <SendAsync>d__0.MoveNext() ilOffset = 0x50 
    at AsyncTaskMethodBuilder`1.Start(TStateMachine& stateMachine) ilOffset = 0x2C 
    at CrmETagMessageHandler.SendAsync(HttpRequestMessage request, CancellationToken cancellationToken) ilOffset = 0x3D 
    at DelegatingHandler.SendAsync(HttpRequestMessage request, CancellationToken cancellationToken) ilOffset = 0x19 
    at <SendAsync>d__0.MoveNext() ilOffset = 0xF 
    at AsyncTaskMethodBuilder`1.Start(TStateMachine& stateMachine) ilOffset = 0x2C 
    at CrmDelegatingHandler.SendAsync(HttpRequestMessage request, CancellationToken cancellationToken) ilOffset = 0x3D 
    at DelegatingHandler.SendAsync(HttpRequestMessage request, CancellationToken cancellationToken) ilOffset = 0x19 
    at <SendAsync>d__0.MoveNext() ilOffset = 0x11D 
    at AsyncTaskMethodBuilder`1.Start(TStateMachine& stateMachine) ilOffset = 0x2C 
    at HttpServer.SendAsync(HttpRequestMessage request, CancellationToken cancellationToken) ilOffset = 0x3D 
    at HttpMessageInvoker.SendAsync(HttpRequestMessage request, CancellationToken cancellationToken) ilOffset = 0x3C 
    at <ProcessRequestAsyncCore>d__0.MoveNext() ilOffset = 0x96 
    at AsyncTaskMethodBuilder.Start(TStateMachine& stateMachine) ilOffset = 0x2C 
    at HttpControllerHandler.ProcessRequestAsyncCore(HttpContextBase contextBase) ilOffset = 0x2C 
    at TaskAsyncHelper.BeginTask(Func`1 taskFunc, AsyncCallback callback, Object state) ilOffset = 0xD 
    at CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() ilOffset = 0xE6 
    at HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) ilOffset = 0x3C 
    at PipelineStepManager.ResumeSteps(Exception error) ilOffset = 0x27A 
    at HttpApplication.BeginProcessRequestNotification(HttpContext context, AsyncCallback cb) ilOffset = 0x31 
    at HttpRuntime.ProcessRequestNotificationPrivate(IIS7WorkerRequest wr, HttpContext context) ilOffset = 0xB0 
    at PipelineRuntime.ProcessRequestNotificationHelper(IntPtr rootedObjectsPointer, IntPtr nativeRequestContext, IntPtr moduleData, Int32 flags) ilOffset = 0x131 
    at PipelineRuntime.ProcessRequestNotification(IntPtr rootedObjectsPointer, IntPtr nativeRequestContext, IntPtr moduleData, Int32 flags) ilOffset = 0x0 
    at UnsafeIISMethods.MgdIndicateCompletion(IntPtr pHandler, RequestNotificationStatus& notificationStatus) ilOffset = 0xFFFFFFFF 
    at UnsafeIISMethods.MgdIndicateCompletion(IntPtr pHandler, RequestNotificationStatus& notificationStatus) ilOffset = 0xFFFFFFFF 
    at PipelineRuntime.ProcessRequestNotificationHelper(IntPtr rootedObjectsPointer, IntPtr nativeRequestContext, IntPtr moduleData, Int32 flags) ilOffset = 0x1E7 
    at PipelineRuntime.ProcessRequestNotification(IntPtr rootedObjectsPointer, IntPtr nativeRequestContext, IntPtr moduleData, Int32 flags) ilOffset = 0x0 
>Crm Exception: Message: The requested record matches a specified If-None-Match version., ErrorCode: -2147088246 
[2017-07-06 08:39:43.344] Process: w3wp |Organization:3eb43172-29f4-dd11-80b4-0015178dc928 |Thread: 39 |Category: Platform |User: 00000000-0000-0000-0000-000000000000 |Level: Error |ReqId: 055f8ace-5e77-4c01-b980-0e97088ed4aa |ActivityId: 055f8ace-5e77-4c01-b980-0e97088ed4aa | CrmODataUtilities.Trace ilOffset = 0x24 
>{"Error":{"InnerError":null,"Message":"CrmHttpException: The requested record matches a specified If-None-Match version."}} 
+0

我會嘗試在香草組織中重新創建問題,以查看它是否只發生在您的組織或平臺錯誤中(在這種情況下,我會將它提交給MS支持團隊)。 –

+0

@FedericoJousset我已經運行了跟蹤工具,它顯示了我的例外情況,請參閱更新。 –

+1

對不起,不幸的是我以前沒有遇到過這個錯誤,並且關於它的信息不是很好。 Web服務錯誤代碼將其描述爲「Dynamics 365中的Wep Api發生故障」。並且它可能與CRM創建的請求(使用If-None-Match標頭)來查詢註釋有關。您可以嘗試使用Fiddler獲取正在生成的請求,以查看是否發現錯誤,但我會將其作爲MS支持團隊的錯誤提出。 –

回答

1

@Dot_NETPro,現在的問題是解決了。

根目錄位於Activity Feeds系統renderOlderPosts函數中,因爲我們在以前的更新包中禁用了它,因爲它在頁面上爲所有用戶引發了空引用異常(因爲MS bug)。該功能似乎沒有被CRM使用,但在下一個更新包中,它開始渲染評論。此外,現在在最新的更新包中修復了空引用異常。