January Problem Solver of the MonthCongratulations to Sourav Dam for be selected in our monthly random drawing, Dynamics Community Problem Solver Sweepstakes.
Read aboug Sourav | Learn how to enter
2020 release wave 1 Discover the latest updates and new features to Dynamics 365 planned through September 2020
Release overview guides and videos Release Plan | Preview 2020 Release Wave 1 Timeline
Ace your Dynamics 365 deployment with packaged services delivered by expert consultants. | Explore service offerings
Connect with the ISV success team on the latest roadmap, developer tool for AppSource certification, and ISV community engagements | ISV self-service portal
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance TechTalks | Customer Engagement TechTalks | Upcoming TechTalks
I've started getting an error when trying to create a rollup or calculated field. My instance is set to Swedish, but the error message translate to something like "Error on XML platform. Invalid fields has been set for this entity."
I started getting the error in my company's instance where I develop. So I resetted another instance and I got the same error, in an instance without any solutions. I also registered for a trial instance, same problem there.
This is the log file from the error message.
Unhandled Exception: System.ServiceModel.FaultException`1[[Microsoft.Xrm.Sdk.OrganizationServiceFault, Microsoft.Xrm.Sdk, Version=184.108.40.206, Culture=neutral, PublicKeyToken=31bf3856ad364e35]]: Attribute new_testt has SourceType 2, but 0 was specified.Detail: <OrganizationServiceFault xmlns:i="www.w3.org/.../XMLSchema-instance" xmlns="schemas.microsoft.com/.../Contracts"> <ActivityId>62e1c536-ef5d-45d8-8bcb-859ecc87ea0f</ActivityId> <ErrorCode>-2147214842</ErrorCode> <ErrorDetails xmlns:d2p1="schemas.datacontract.org/.../System.Collections.Generic" /> <Message>Attribute new_testt has SourceType 2, but 0 was specified.</Message> <Timestamp>2018-09-11T19:30:52.6820103Z</Timestamp> <ExceptionRetriable>false</ExceptionRetriable> <ExceptionSource i:nil="true" /> <InnerFault i:nil="true" /> <OriginalException i:nil="true" /> <TraceText i:nil="true" /></OrganizationServiceFault>
Is this a known issue?
If you have already verified that this happens on multiple instances and even on a new trial then this is most likely a bug introduced recently. However with that said, I tried it on my trial organization and I am able to create the rollup field without any issues. My version is Version 1710 (220.127.116.112) online.
If this doesn't fix then you can contact MS Support https://admin.dynamics.com
Hope this helps.
This is my thought as well. I'm running Version 1710 (18.104.22.1689) Online.
Will contact MS Support as soon as possible.
I have the same problem in an Online Environment, 22.214.171.1249.
Many thank in advance
No solutions found yet.
I have an open support ticket with Microsoft as we speak.
I have the same issue in all my customer's instances based on version 1710 (126.96.36.1999). But not in one instance based on version 1710 (188.8.131.520).
I've also realized I can't edit any of the formulas from OOB or custom calculated and rollup fields. The "Edit" button (for editing the formula) is hidden and the field appears as Basic type instead of Calculated or Rollup.
Did you have any response from MS Support?
I have spoken to a MS representative that escalated the issue and gave me a time slot with a technician 09:00 GMT+2 tomorrow.
I review this code this is not a known issue as well, but I am facing the same issue, after that I am trying so many processes to solve it out, but I can't. after that I take a help of supportnumbers.net/toshiba-support to solve my issue quickly. it really helps e to a lot to solve this properly, if you are interested you can also take a help of this site, I think your problem will be solved properly.
I have the some problem. Microsoft will fix the issue in about two weeks.
Hi again Viktor.
We also opened a new support ticket. It looks it's a known issue and it will be fixed soon (this week or next week).
Our environment just got patched to Version 1710 (184.108.40.2068). Everything is back to normal for us.
Business Applications communities