Finance | Project Operations, Human Resources, ...

Schedule API for Project Task issue (msdyn_PssCreateV1)

(0) Share

Report

Posted on by Community Member

I have been testing the Project and Project Task creation APIs and found what I believe to be an odd bug. Has anyone else experienced this?

I am creating projects via the msdyn_CreateProjectV1 Action. That is working fine.

I am then trying to add Project Tasks to the above projects (using

msdyn_CreateOperationSetV1

msdyn_PssCreateV1

msdyn_ExecuteOperationSetV1)

and having mixed results with sometimes it working and other times the operationset is Pending. I have been able to recreate this as follows:

Scenario 1:
1. Create the Project using API (msdyn_CreateProjectV1)
2. WITHOUT going to the model app Project and opening Task Tab,
  1. create Project Tasks using API (no errors so different from Scenario 2)
3. RESULT: OperationSet is Pending and tasks are not created
Scenario 2:
1. Create the Project using the New button in the Model App.
2. WITHOUT going to the model app Project and opening Task Tab,
  1. create the Project Tasks using the API
3. RESULT: ERROR on GetDefaultBucket query (per sample code docs.microsoft.com/.../schedule-api-preview)
  1. - Exception Message: Please open project with id 2589ac45-0df6-eb11-94ef-0022481e1656 in the Dynamics UI and navigate to the Tasks tab
4. Go to Project in model app and open Task tab and wait for it to open
5. Close Project form in model app.
6. Re-run the create of Project Tasks using the API
7. RESULT: OperationSet is Complete and tasks are created as expected
Scenario 3:
1. Create the Project using API (msdyn_CreateProjectV1)
2. Go to Project in Model app and click on the Task tab. Close form after Task tab loads.
3. create Project Tasks using API
4. RESULT: OperationSet is Complete and tasks are created as expected

Can anyone explain this behavior and why it is “Pending” and what needs to be done to complete it? If creating tasks for a Project, is there a pre-requisite that the Task tab must be opened in Model app form manually first?

I have the same question (0)

All responses (11)

Answers (0)

Suggested answer

apa 8,284 Moderator on at

Like (0)

Report
RE: Schedule API for Project Task issue (msdyn_PssCreateV1)

Hi JanetTh.

The msdyn_CreateProjectV1 action also creates a default bucket. When you use that and then create a task with msdyn_PssCreateV1, you must use the @odata.bind annotation for msdyn_projectbucket. Please see my post here on the APIs and the sample JSON below for Power Automate and Postman scenarios. The JSON is for creating tasks.

{ "Entity": { "msdyn_LinkStatus": 192350000, "msdyn_subject": "", "msdyn_start": "", "msdyn_finish": "", "@odata.type": "", "msdyn_project@odata.bind": "", "msdyn_projectbucket@odata.bind": "" }, "OperationSetId": "" }

When you create a new project row in the model-driven UI, a default bucket is not created until you navigate to the Task tab. That's why you can't create tasks before the bucket is there. However when you use msdyn_CreateProjectV1, a default bucket is automatically created. Your scenario 1 should work so the process is:

1. Create project using msdyn_CreateProjectV1.

2. Create OperationSet.

3. Create a task using msdyn_PssCreateV1. Remember all relevant OData binds!

4. Execute the OperationSet with msdyn_ExecuteOperationSetV1.

The feature is in preview so outages and changes may occur.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

RE: Schedule API for Project Task issue (msdyn_PssCreateV1)

Thanks - I had seen your post before and was very useful. I am using a C# plugin triggered from a custom entity populated by a integration job for our POC testing rather than PowerAutomate but when we move to PA I'm sure it will be very useful.

Since my Scenario 3 works and Scenario 1 does not and only difference is opening the Task tab, I think this is MSFT bug. I am following the process you mentioned and have not been able to find any documentation on what the OperationSet status of "Pending" means so will raise ticket with MSFT.

Was this reply helpful? Yes No
apa 8,284 Moderator on at

Like (1)

Report

RE: Schedule API for Project Task issue (msdyn_PssCreateV1)

I'd repro the scenario in Postman and if it doesn't work, open a service request. At least in my geo the APIs are working when called from custom connectors.

Was this reply helpful? Yes No
taral 196 on at

Like (0)

Report

RE: Schedule API for Project Task issue (msdyn_PssCreateV1)

Hello Antii,

I 'm creating project tasks using Flow using below article

daytodaydynamics365.com/.../

in my scenario project task will be multiple so when i'm trying to generate tasks using psscreatev1 command in apply to each step.

the flow gives below error and not able to save the flow.

Below are my steps of the flow.

can you suggest what can be the issue.

Was this reply helpful? Yes No
Suggested answer

apa 8,284 Moderator on at

Like (2)

Report
RE: Schedule API for Project Task issue (msdyn_PssCreateV1)

Hi Taral Shah.

I can see two things there in the JSON:

msdyn_activitynumber. That's most likely whole number column so it doesn't require quotes. Instead of "1" just punch in 1.

The actual error in the JSON is probably because of the @ sign with the @odata.type property. You need to escape it with another @. I.e. punch in @@odata.type. Another options is to store @odata.type in a a compose action in which case you don't need to escape the @.

{ "Entity": { "msdyn_LinkStatus": 192350000, "msdyn_subject": "taskSubjectHere", "msdyn_start": "yyyy-MM-ddTHH:mm:ssZ", "msdyn_finish": "yyyy-MM-ddTHH:mm:ssZ", "@@odata.type": "Microsoft.Dynamics.CRM.msdyn_projecttask", "msdyn_project@odata.bind": "msdyn_projects(projectGuidHere)", "msdyn_projectbucket@odata.bind": "msdyn_projectbuckets(bucketGuidHere)" }, "OperationSetId": "operationSetIdHere" }

Was this reply helpful? Yes No
taral 196 on at

Like (0)

Report

RE: Schedule API for Project Task issue (msdyn_PssCreateV1)

Hello Antti,

i have done changes as per your recomnedations and error resolved.

but getting below error while running the flow.

{

  "error": {

    "code": "0x80040265",

    "message": "ScheduleAPI-OV-0006:fc98dff7-818a-ec11-93b0-6045bdaa978f: The current user with AADId 988e6660-0f0c-4792-a48d-e7dd7aeafbab is different from the owner with AADId 54b41df7-52a4-4b33-9c85-c7362e97d6f0 of the operation set."

  }

}

Can you suggest what can be the issue?

Was this reply helpful? Yes No
apa 8,284 Moderator on at

Like (2)

Report

RE: Schedule API for Project Task issue (msdyn_PssCreateV1)

That error is given when an OperationsSet is created by user a) and called by user b). You have to create and call with the same user.

Was this reply helpful? Yes No
taral 196 on at

Like (0)

Report

RE: Schedule API for Project Task issue (msdyn_PssCreateV1)

Hello Antti,

The issue got resolved by your answer but now while creating OperationSet i'm getting below error in MS flow.

"ScheduleAPI-OV-0004:00000000-0000-0000-0000-000000000000: The maximum number of operation set allowed per user is 10."

Was this reply helpful? Yes No
apa 8,284 Moderator on at

Like (2)

Report

RE: Schedule API for Project Task issue (msdyn_PssCreateV1)

That means that there are 10 open OperationSets for the user:
https://docs.microsoft.com/en-us/dynamics365/project-operations/project-management/schedule-api-preview#limitations-and-known-issues

You need to either abandon them manually or wait for the OOTB flows Project Service Core - Abandon Open Operation Sets or Project Service Core - Abandon Pending Operation Set to run.

Was this reply helpful? Yes No
taral 196 on at

Like (0)

Report

RE: Schedule API for Project Task issue (msdyn_PssCreateV1)

Hey Antii,

Issue got resolved by following your link i have added one another step of abondonprocess.

Thanks for suggestions.

Regards,

Taral Shah

Was this reply helpful? Yes No