none
CustomFieldRequiedValueNotProvided issue - Proj Server 2007 / WSS 3.0 RRS feed

  • Question


  • Hi,

     

    Context: I am building a C# interface for updating projects with project custom field information. The error only occurs when the DataSet includes a certain custom field however, it looks as if all the required data from that custom field is inserted.

    Error: I am receiving a CustomFieldRequiedValueNotProvided error when using the QueueUpdateProject web service method.

    Process used in code: Initially i loop through a list of projects, for each project in the list i do a ReadProjectEntities to grab a smaller DataSet. With this dataset i update the project custom field information that has changed. I then do a .GetChanges(); to reduce the DataSet futher. Followed the code below to commit the changes to the project server:

     

     jobId = Guid.NewGuid();
    project_WebSvc.QueueUpdateProject(jobId, sessionId, singleProj, false );
    WaitForQueue(jobId);
    jobId = Guid.NewGuid();
    project_WebSvc.QueueCheckInProject(jobId, projGuid, true , sessionId, sessionDesc);
     WaitForQueue(jobId);

    jobId = Guid.NewGuid();
    project_WebSvc.QueuePublish(jobId, projGuid, true , String.Empty);
    WaitForQueue(jobId);

    Below is a DataSet that works when updated using QueueUpdateProject:

    CUSTOM_FIELD_UID PROJ_UID MD_PROP_UID MD_PROP_ID FIELD_TYPE_ENUM FLAG_VALUE TEXT_VALUE DATE_VALUE CODE_VALUE DUR_VALUE NUM_VALUE DUR_FMT INDICATOR_VALUE
    34350aec-7383-4a79-8930-3434f2634875 1cfb1af9-a4c1-47e9-a8a8-0136fb415d01 000039b7-8bbe-4ceb-82c4-fa8c0b400419 188744729 21   14793            
    02923b0a-ebb3-4cb3-a7ef-e52905f7f9a2 1cfb1af9-a4c1-47e9-a8a8-0136fb415d01 000039b7-8bbe-4ceb-82c4-fa8c0b40041a 188744730 21   OR99W:PACIFIC HWY W OVER SW MULTNOMAH BL (#02010)            
    74e1bd84-eb18-4694-9fb8-cf79cf5f04d9 1cfb1af9-a4c1-47e9-a8a8-0136fb415d01 000039b7-8bbe-4ceb-82c4-fa8c0b40041c 188744732 21       ff1b6037-9c6e-4cda-a735-94827dd6b475        
    c51982e8-d427-43a6-a5ea-52fbaac63880 1cfb1af9-a4c1-47e9-a8a8-0136fb415d01 000039b7-8bbe-4ceb-82c4-fa8c0b400422 188744738 21       27c89bf1-34ef-4a4b-b1bd-594ce8527730        
    9cdb39ce-6777-48ed-a56b-feebd89dc45a 1cfb1af9-a4c1-47e9-a8a8-0136fb415d01 000039b7-8bbe-4ceb-82c4-fa8c0b400423 188744739 21       b87c7b37-3641-4e59-b70d-fb5af7865dc3        

    This DataSet Does not work:

    CUSTOM_FIELD_UID PROJ_UID MD_PROP_UID MD_PROP_ID FIELD_TYPE_ENUM FLAG_VALUE TEXT_VALUE DATE_VALUE CODE_VALUE DUR_VALUE NUM_VALUE DUR_FMT INDICATOR_VALUE
    842a5d6a-f76e-465a-baa5-805825d691c6 8dfe606f-c481-4784-8e3a-002ae9a6ad55 000039b7-8bbe-4ceb-82c4-fa8c0b40035b 188744539 4     6/18/2009 12:00:00 AM          
    cdc4fd59-de26-4610-8333-d482bb42f753 8dfe606f-c481-4784-8e3a-002ae9a6ad55 000039b7-8bbe-4ceb-82c4-fa8c0b400419 188744729 21   16360            
    a85d95de-88c1-460b-9772-08da8552033c 8dfe606f-c481-4784-8e3a-002ae9a6ad55 000039b7-8bbe-4ceb-82c4-fa8c0b40041a 188744730 21   BEAR GULCH SLIDE DRAINAGE TUNNEL REPAIR            
    e80f6315-7d53-47ed-9fc7-62a355a4c865 8dfe606f-c481-4784-8e3a-002ae9a6ad55 000039b7-8bbe-4ceb-82c4-fa8c0b40041c 188744732 21       8ed3776a-837a-4faf-b305-a3271fd65b45        
    803df15a-0398-469b-a999-7b4ba1200ce9 8dfe606f-c481-4784-8e3a-002ae9a6ad55 000039b7-8bbe-4ceb-82c4-fa8c0b400422 188744738 21       add51e86-afa3-451c-a96e-e6873a0ca0af        
    2fb652a9-60c8-4bf1-a91f-1f2b5119aed2 8dfe606f-c481-4784-8e3a-002ae9a6ad55 000039b7-8bbe-4ceb-82c4-fa8c0b400423 188744739 21       36eadd40-e59b-49ff-be93-4642a76bf475        
    38901ce3-9555-4e01-899e-b07c70658987 8dfe606f-c481-4784-8e3a-002ae9a6ad55 000039b7-8bbe-4ceb-82c4-fa8c0b400424 188744740 21   FY09SP03000            
    Tuesday, January 18, 2011 4:07 PM

All replies

  • Hi Craigaw,

    it's difficult to say with this informations, but, you get this error basically when try to submit a dataset without a value for a RequiredCustomField or submit a wrong reference for a lookup table values for a custom field.

    With some incremental test, you can find what custom field value is wrong.

    Maybe a wrong code_value or maybe, for the last custom field in the second dataset, you must provide a code_value and not a text_value as i can see in the sample.

    I hope this help you,

    Best Regards,

    Paolo

    Tuesday, January 25, 2011 10:46 PM