Skip to main content

Notifications

Announcements

No record found.

Microsoft Dynamics 365 | Integration, Dataverse...
Answered

Error with lead form on model-driven App

(0) ShareShare
ReportReport
Posted on by 280
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?
  • Armine DD Profile Picture
    Armine DD 280 on at
    RE: Error with lead form on model-driven App

    Hi Ankit,

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

    Thank you for the response and details,

    All the best, Armine

  • Verified answer
    RE: Error with lead form on model-driven App

    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.

     

     

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

Congratulations 2024 Spotlight Honorees!

Kudos to all of our 2024 community stars! 🎉

Meet the Top 10 leaders for December!

Congratulations to our December super stars! 🥳

Get Started Blogging in the Community

Hosted or syndicated blogging is available! ✍️

Leaderboard

#1
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 291,602 Super User 2024 Season 2

#2
Martin Dráb Profile Picture

Martin Dráb 230,340 Most Valuable Professional

#3
nmaenpaa Profile Picture

nmaenpaa 101,156

Leaderboard

Product updates

Dynamics 365 release plans