Loading...
Quick Links

Enterprise field name constraints

Home Forums Discussion Enterprise field name constraints

Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts
  • #418481 Reply
    Brian Mijas
    Participant

    Using MS Project Server (Project Online 2016) and trying to find out if there are any Enterprise field name constraints for Task related fields. I ask because we recently (2 weeks ago) created a new Task field “Application”, refreshed Power BI to see the new field, populated it in MS Project and expected to be able to report on it in Power BI. We can see the field in PBI but no data has pulled across. The only reason we can come up with is a naming constraint, but have been unable to find any documentation relating to that.

    Any pointers most gratefully received.
    Cheers
    Brian

    #418482 Reply
    Larry ChristofaroLarry Christofaro
    Participant

    Brian, I do not know of any constraints and don’t have an answer to your question. I’m responding in case you get an answer from others. Good luck…

    #418486 Reply
    Brian Mijas
    Participant

    Hey Larry, thanks for the response, I’ve been doing some testing myself and it looks as though, if you call a new Task field Application and make it a text field it’s auto assigned to one of the Text1-20 fields, which don’t get exported to Power BI. Naming the field to something else, Prj_Appl for example, it picks up as a plain field without a problem.

    I guess we can close off this query

    Rgds
    Brian

    #418487 Reply
    Larry ChristofaroLarry Christofaro
    Participant

    Thanks Brian, good to know. It’s not a reserved word in either Project or Project Online but PBI must have a separate constraint.

Viewing 4 posts - 1 through 4 (of 4 total)
Reply To: Enterprise field name constraints
Your information: