web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Microsoft Dynamics 365 | Integration, Dataverse... / Error with lead form o...
Microsoft Dynamics 365 | Integration, Dataverse...
Answered

Error with lead form on model-driven App

(4) ShareShare
ReportReport
Posted on by Armine DD 288
Hi experts,
We are experiencing error with model-driven application, opening Lead entity main form gives the error. Here are the details: Error
Something has gone wrong. Check technical details for more details.
  • Technical DetailsError Code: -2147015424
  • Session Id: bc209d4e-3f91-4921-a0a4-5fd67ac228ef
  • Activity Id: ce3ad6bb-5b0e-463e-b28c-e4b7bf45cd41
  • Timestamp: Thu Apr 23 2020 15:37:48 GMT+0400 (Armenia Standard Time)
Could not find a property named 'customeridname' on type 'Microsoft.Dynamics.CRM.lead'.
at Microsoft.OData.UriParser.SelectPathSegmentTokenBinder.ConvertNonTypeTokenToSegment(PathSegmentToken tokenIn, IEdmModel model, IEdmStructuredType edmType, ODataUriResolver resolver, BindingState state) at Microsoft.OData.UriParser.SelectPropertyVisitor.ProcessTokenAsPath(NonSystemToken tokenIn) at Microsoft.OData.UriParser.SelectPropertyVisitor.Visit(NonSystemToken tokenIn) at Microsoft.OData.UriParser.SelectBinder.Bind(SelectToken tokenIn) at Microsoft.OData.UriParser.SelectExpandBinder.Bind(ExpandToken tokenIn) at Microsoft.OData.UriParser.SelectExpandSemanticBinder.Bind(ODataPathInfo odataPathInfo, ExpandToken expandToken, SelectToken selectToken, ODataUriParserConfiguration configuration, BindingState state) at Microsoft.OData.UriParser.ODataQueryOptionParser.ParseSelectAndExpandImplementation(String select, String expand, ODataUriParserConfiguration configuration, ODataPathInfo odataPathInfo) at Microsoft.OData.UriParser.ODataQueryOptionParser.ParseSelectAndExpand() at Microsoft.Crm.Extensibility.OData.CrmODataServiceDataProvider.ThrowIfExpandWithRefForNonLookupNavProp(ODataQueryOptions queryOptions, String edmEntityName) at Microsoft.Crm.Extensibility.OData.CrmODataServiceDataProvider.RetrieveEdmEntity(CrmODataExecutionContext context, String edmEntityName, String entityKeyValue, ODataQueryOptions queryOptions) at Microsoft.Crm.Extensibility.OData.EntityController.GetEntityImplementation(String& entityName, String key) at Microsoft.PowerApps.CoreFramework.ActivityLoggerExtensions.Execute[TResult](ILogger logger, EventId eventId, ActivityType activityType, Func`1 func, IEnumerable`1 additionalCustomProperties) at Microsoft.Xrm.Telemetry.XrmTelemetryExtensions.Execute[TResult](ILogger logger, XrmTelemetryActivityType activityType, Func`1 func) at lambda_method(Closure , Object , Object[] ) at System.Web.Http.Controllers.ReflectedHttpActionDescriptor.ActionExecutor.<>c__DisplayClass10.<GetExecutor>b__9(Object instance, Object[] methodParameters) at System.Web.Http.Controllers.ReflectedHttpActionDescriptor.ExecuteAsync(HttpControllerContext controllerContext, IDictionary`2 arguments, CancellationToken cancellationToken) --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at System.Web.Http.Controllers.ApiControllerActionInvoker.<InvokeActionAsyncCore>d__0.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at System.Web.Http.Controllers.ActionFilterResult.<ExecuteAsync>d__2.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at System.Web.Http.Dispatcher.HttpControllerDispatcher.<SendAsync>d__1.MoveNext()
Opening Lead Quick Create form gives similar error, same type of error happens with Contact entity Main and Quick Create forms in the App, but all forms work with no error in desktop version.
My initial guess was lookup for Client, but the field schema name is customerid, not customeridname. 
Anyone has experienced this with Apps?
I have the same question (0)
  • Verified answer
    Ankit Sabharwal Profile Picture
    Ankit Sabharwal on at

    Hy Armine,

    Hope this post finds you well.

    This seems to be known issue with the product and Microsoft PG team has acknowledged it.

    Right now current workaround is , we need to remove the last name from Linkedin Section from the lead form and then it can be used.

    One more thing , you need to go the field customerid and check whether the custom control is enabled fro it. if yes then we need to remove that binding of LinkedInsalesNavigator.

    Hope this post helps you out.

    Best regards,

    Ankit

    Please mark as verified if the answer is helpful. Welcome to join hot discussions in Dynamics 365 Forums.

     

     

  • Armine DD Profile Picture
    Armine DD 288 on at

    Hi Ankit,

    yes, that is exactly what we did with MS support technician.

    Thank you for the response and details,

    All the best, Armine

  • Fuechsin Profile Picture
    Fuechsin 21 on at
    (To whom it may concern...)

    I had a similar problem.
     
    When opening an account form in the user interface or in the editor, these were the following error details (I anonymized some details) - please note that the mentioned field "sth_data_dataversion_str" had already been deleted from the environment about 5 to 10 days ago and there was no reference left (no javascript, no code, no webresource of any kind and so on):
     
    Microsoft.OData.ODataException: Could not find a property named 'sth_data_dataversion_str' on type 'Microsoft.Dynamics.CRM.account'. at Microsoft.OData.UriParser.SelectPathSegmentTokenBinder.ConvertNonTypeTokenToSegment(PathSegmentToken tokenIn, IEdmModel model, IEdmStructuredType edmType, ODataUriResolver resolver, BindingState state) at Microsoft.OData.UriParser.SelectExpandBinder.ProcessSelectTokenPath(PathSegmentToken tokenIn) at Microsoft.OData.UriParser.SelectExpandBinder.GenerateSelectItem(SelectTermToken tokenIn) at Microsoft.OData.UriParser.SelectExpandBinder.Bind(ExpandToken expandToken, SelectToken selectToken) at Microsoft.OData.UriParser.SelectExpandSemanticBinder.Bind(ODataPathInfo odataPathInfo, ExpandToken expandToken, SelectToken selectToken, ODataUriParserConfiguration configuration, BindingState state) at Microsoft.OData.UriParser.ODataQueryOptionParser.ParseSelectAndExpandImplementation(String select, String expand, ODataUriParserConfiguration configuration, ODataPathInfo odataPathInfo) at Microsoft.OData.UriParser.ODataQueryOptionParser.ParseSelectAndExpand() at Microsoft.Crm.Extensibility.OData.DataQueryOptionsConverter.BindSelectExpand(EntityExpression qe, SelectExpandQueryOption selectExpandQueryOption)
    UciError: Microsoft.OData.ODataException: Could not find a property named 'sth_data_dataversion_str' on type 'Microsoft.Dynamics.CRM.account'. at Microsoft.OData.UriParser.SelectPathSegmentTokenBinder.ConvertNonTypeTokenToSegment(PathSegmentToken tokenIn, IEdmModel model, IEdmStructuredType edmType, ODataUriResolver resolver, BindingState state) at Microsoft.OData.UriParser.SelectExpandBinder.ProcessSelectTokenPath(PathSegmentToken tokenIn) at Microsoft.OData.UriParser.SelectExpandBinder.GenerateSelectItem(SelectTermToken tokenIn) at Microsoft.OData.UriParser.SelectExpandBinder.Bind(ExpandToken expandToken, SelectToken selectToken) at Microsoft.OData.UriParser.SelectExpandSemanticBinder.Bind(ODataPathInfo odataPathInfo, ExpandToken expandToken, SelectToken selectToken, ODataUriParserConfiguration configuration, BindingState state) at Microsoft.OData.UriParser.ODataQueryOptionParser.ParseSelectAndExpandImplementation(String select, String expand, ODataUriParserConfiguration configuration, ODataPathInfo odataPathInfo) at Microsoft.OData.UriParser.ODataQueryOptionParser.ParseSelectAndExpand() at Microsoft.Crm.Extensibility.OData.DataQueryOptionsConverter.BindSelectExpand(EntityExpression qe, SelectExpandQueryOption selectExpandQueryOption) at s (https://content.powerapps.com/resource/u...b/scripts/app....6.js:33:9...5) at new m (https://content.powerapps.com/resource/u...b/scripts/app....6.js:28:1...8) at m.fromLegacyErrorStatus (https://content.powerapps.com/resource/u...b/scripts/app....6.js:28:165071) at O (https://content.powerapps.com/resource/u...b/scripts/app....6.js:28:1...2) at https://content.powerapps.com/resource/u...b/scripts/app....6.js:33:2...9
     
    I did not find the true reason for the error but I succceeded to remove it.

    My solution:

    As I already mentioned above: sth_data_dataversion_str was a field that I had already deleted at least 5 days ago from the environment.

    So now I created this field "sth_data_dataversion_str" anew and put in on the form, published the form and did a "publish all" (to be absolutely sure it's published :-))
    Tested: no error was thrown (UI, editor)
     
    Removed the field "sth_data_dataversion_str" from the form and published / published all
    Tested: no error was thrown (UI, editor)
     
    Deleted the field "sth_data_dataversion_str" from the environment, published all
    Tested: no error was thrown (UI, editor)
     
    Done! 👍
     
     
     

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Congratulations to the November Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > Microsoft Dynamics 365 | Integration, Dataverse, and general topics

#1
#ManoVerse Profile Picture

#ManoVerse 101

#2
Siv Sagar Profile Picture

Siv Sagar 93 Super User 2025 Season 2

#3
Martin Dráb Profile Picture

Martin Dráb 62 Most Valuable Professional

Last 30 days Overall leaderboard

Featured topics

Identifying an Org as CDS or Dynamics
Get batch job history log from D365 FO to Power Automate
Gross and Net Weight of Shipments feeding back into Sales Order (from External Source)

Product updates

Dynamics 365 release plans