Hi, I’m trying to create projects using Create a project and with the body of my project data, I have a bunch of custom_fields. However, this code fails, probably since I need to add the projects to a certain portfolio carrying those custom fields - before I can say that the project should have specific values for them.
Trying to update an existing project allready in that portfolio, using custom fields works fine.
I wonder - what’s the purpose of listing custom_fields as a possible parameter in the data object of https://app.asana.com/api/1.0/projects since it will fail in all cases. When a project is created, it’s not part of any portfolio, thus can not carry custom_fields data, right?
Or is that just how the API is documented since it’s a similar URL for update project ?
I believe that’s simply a shortcut the team took, because I agree with you, I don’t see a scenario where you could create the project and have those fields available.
Yes, I agree with the above discussion: I don’t see how you could add a custom field value when creating a project since, as said above, it doesn’t yet belong to a portfolio.
Yes, I think because custom fields exist on a project object overall, it shows up in the docs that way, even though it can’t be added on a “create project” call.
@John_Vu@Andrew-asana does that make sense? Would there be any way to remove “custom fields” from the property list for “create project”?
