SanshaKuvakei

My feedback

  1. 135 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    9 comments  ·  Project Online  ·  Flag idea as inappropriate…  ·  Admin →
    SanshaKuvakei supported this idea  · 
    An error occurred while saving the comment
    SanshaKuvakei commented  · 

    Hey Nadin,
    we face the same problem here, and the local custom fields are not read-only in PSI, you can update these values easily. But our use case is that you have project related lookup table. For example if you want to map a task to an wbs element in an external system. The wbs elements are always project dependent. Until now it was easy to use for the customer cause we were able to provide the correct values into an local custom field which had these values as lookup table per project. Without them, you have to use an enterprise custom field with one lookup table for all projects which results at our customers in a lookup table with > 10000 entries. And this is not usable and we cannot argue for such a scenario, besides that, you are not able to maintain lookup table of this size, cause everything crashes or runs into timeouts. But there are even more scenarios out there.
    I hope this illustrates the problem for you.

    Regards

    PS: There is a nice discussion going on at the forums (https://social.msdn.microsoft.com/Forums/en-US/bfe5b6ed-63ad-4d0d-8c58-1b81c193b20a/microsoft-does-not-provide-a-supported-way-to-read-all-useful-task-data-from-project-online?forum=project2010custprog).

Feedback and Knowledge Base