Skip to main content
Nintex Community Menu Bar
Solved

The property 'OriginatorId' does not exist on type

  • Feb 9, 2017 2:17 PM UTC
  • 6 replies
  • 122 views
  • Translate All
Forum|alt.badge.img+6

Hello, wondering if someone had a similar issue like this:

Created a column 'Originator' in the list

Added action to set the field Originator with value of CreatedBy

When I run the workflow I get the below weird error which I don't understand:

Anyone a tip why this happens ?

Thanks

Jaap

 

Activity in progress

 

Retrying last request. Next attempt scheduled after 2/9/2017 2:12 PM. Details of last request: HTTP BadRequest to https://pathetc/_api/web/lists(guid'8b2f8173-74c6-409f-bb4f-ba4eb4f70ecc')/Items(17) Correlation Id: eba50ffd-80c3-e49c-8031-b5ee1e1b2461 Instance Id: 1adda41b-3bcd-48fc-b8b0-e92e9333c5db

 

The property 'OriginatorId' does not exist on type 'SP.Data.PAD_x0020_RequestsListItem'.

Make sure to only use property names that are defined by the type.
Retry now               

Best answer by jaapsteenis

Yes we called ite Requester :-) but if you have loaded a history of 2000 records and need to run a workflow to fill that field again, I am not going to love that extra work :-)

View original

    6 replies

    Forum|alt.badge.img+12
    • xMikeX
    • Feb 10, 2017 1:53 AM UTC

    Are you sure you are using the correct spelling of the name when setting the field?  Curious because you said "Originator" but later said "OriginatorId"

    Translate
    Forum|alt.badge.img+6
    • jaapsteenis
    • Author
    • Feb 10, 2017 10:25 PM UTC

    When you use a column ''Originator in your design, the problem is present. So I am wondering if this is a Nintex Bug ?

    Translate
    Forum|alt.badge.img+12
    • xMikeX
    • Feb 10, 2017 10:39 PM UTC

    I've run into issues in the past with certain "reserved" column names and have observed the same thing.  For example list lookup fails if you have a column name such as DisplayName that is the same as an item property in Sharepoint.

    Translate
    Forum|alt.badge.img+6
    • jaapsteenis
    • Author
    • Feb 10, 2017 10:47 PM UTC

    Hi Mike, yes got that same feeling too with reserved fields. A column like Originator is a standard column every user would define as valid column in his/her design isn't it ?

    I think that Nintex must address this as this frustrates like hell and did take me roughly 2 hours to correct.

    Translate
    Forum|alt.badge.img+12
    • xMikeX
    • Feb 10, 2017 10:50 PM UTC

    Without checking, I say it certainly sounds like one.  Why not just change the column name to something else and test, see if you get better results?

    Translate
    Forum|alt.badge.img+6
    • jaapsteenis
    • Author
    • Answer
    • Feb 11, 2017 9:22 AM UTC

    Yes we called ite Requester :-) but if you have loaded a history of 2000 records and need to run a workflow to fill that field again, I am not going to love that extra work :-)

    Translate
    Sidebar Buttons
    Nintex Community Home Contact Nintex Support Email Nintex Community Check Nintex Status
    Terms & ConditionsAccessibility statement