Beauty thanks guys, ill give it a crack Phil 
1 Like
Got the same fail message here, suddenly our automation stopped working because of this. We work with Zoho Flow, and it worked fine before. Is there any way it can be rolled back? We don’t have any experience with API / programming. Zoho Flow is just a interactive flowchart kinda tool.
We told asana a few days ago about the Microsoft integration, and they reached out to them. I’ll let them know about Zoho as well. You need to go around and make direct API calls I am afraid…
1 Like
Received this error email from our Salesforce automation
Apex script unhandled exception by user/organization: 005f2000009DRzi/00Df2000000DMKr
Organization: Bible League Canada (blc.my.salesforce.com).
Failed to invoke future method ‘public static void createCustom(Map<String,String>)’ on class ‘AsanaPublic.AsanaProject’ for job id ‘707JQ00000n84BW’
caused by: AsanaPublic.AsanaProject.ProjectCreationException: Cannot create Project. Error:(You cannot pass the
publicfield while opting-in for the privacy_setting feature.)Class.AsanaPublic.AsanaProject.createCustom: line 718, column 1
Wondering if anyone has been successful in solving this with Salesforce or are we in a similar boat as Microsoft Integration users where we may be waiting on Salesforce to make changes. This is definitely a bit outside of my wheelhouse so happy to reach out to Salesforce Support if that is the best path forward.
@David_Rowaan - from your error message (and assuming you are using some kind of Salesforce automation tool), I think you’ll need to contact them, as that error message suggests that the call they’re making on your behalf is not set up correctly (due to these permission changes, presumably).
Yes, afraid you are. As @Stephen_Li says, you should reach out to Salesforce and let them know that Asana has removed the public property from their Project object, so Salesforce needs to update their Asana API calls so as to remove that property from them.
1 Like
What is the current plan for the private_to_team value? Is it still scheduled to be deprecated as mentioned in an earlier post by @John_Baldo? If so, when will this deprecation occur?
1 Like
I scrolled for a bit and didnt see anything on this topic so please forgive me if I missed it. But for those of us who use the DITTO platform to frequently transfer projects between Workspaces (should really be a simple feature native in Asana by now)… this change is impacting transfers. There is no setting that I’m able to identify that allows transfer via this API platform now. All transfers, despite team or project privacy settings come back as errors due to privacy settings.
The error: “You cannot pass the public field while opting-in for the privacy_setting feature.”
This is being encountered on all Team and Project privacy settings. We’ve tried all with no luck.
We transfer Project templates multiple times per month and need to be able to continue using this platform immediately. What solutions are there for the roadblock this privacy change is creating?
1 Like
Hi @Kothar,
Is there any chance you might be able to address this in your incredible Ditto app?
I’m just looping you in to @Jenna_Gable’s report here; I haven’t run into this because I haven’t had occasion to use Ditto recently.
It would be great to know because I often link to Ditto in answers in the Forum and refer clients.
Thanks,
Larry
1 Like
Thank you. I sent requests for assistance there first, but haven’t received a response. When I located this thread and saw so many other platforms are now having similar issues, I was hoping to either learn a workaround or see if Asana has/is planning a resolution for this new headache.
1 Like
I am also running into the same issue using the Ditto app and haven’t been able to get a response from the developer. We are stuck with lots of customers upset we can’t get their templates installed. This change Asana made is really frustrating and as @Jenna_Gable said, transferring projects between workspaces seems like an obvious feature Asana should have thought about.
1 Like
I just emailed the creator of Ditto to make sure he’s aware.
Thanks,
Larry
1 Like
Hey All,
Sorry for the late reply here. Since your posts a few weeks ago, we have been working on another round of communication with these integration partners. To give you a sense of what we’ve done to date:
- We posted here a year ago to make people aware of the upcoming change.
- To avoid broader impact, we have adjusted our plan and made the field read-only rather than removing it completely.
- About a couple months ago, we sent direct email communication about this change to those who would be impacted (based on previous API traffic).
- Since your posts here, we have sent another round of communication to integrations developers who are still attempting to use the field.
I appreciate that this is impacting your workflows. Because we’ve done this communication, are seeing a relatively low error rate, and have provided a way to opt-out for now, we are not planning to roll back the change.
We’re doing everything we can to contact integration developers. We appreciate your assistance with that!
Apologies for the impact. We’re continuously improving our change process and doing our best to minimize any breaking changes.
1 Like
How are we able to opt out of this change so we can continue to use tools like Ditto until the issues are worked out?
I’m afraid there’s no workaround for apps that haven’t been updated.
Sorry,
Larry
Circling back since we were both experiencing the same major issue.
Have you heard of anyone getting a response from Ditto’s developer yet? I don’t see any 2024 updates on the site and haven’t gotten any reply to my messages or comments. How about you? 
Thanks for this update. I’m not sure I understand an item or two in there, so some clarification would be so helpful.
-
Can you confirm if the “read only” change instead of total removal, is a new adjustment? I’m not certain this helps us, but want to be sure I understand.
-
Can you clarify the opt out portion of your message? @CandiceCoppola asked if we can opt out and I don’t see an answer. If you can confirm if this is possible and how/where to opt out of this for the tine being, I’m sure we’d all greatly appreciate it.
1 Like
Unfortunately Jenna, I haven’t heard a thing from the Ditto team. Very disappointing. I’ve had to resort to manually installing templates which as you know - is not fun. I wish there was some kind of alternative and that Asana made this process easier
Hi @CandiceCoppola, @Jenna_Gable, @lpb,
Sorry that Ditto has been impacted by this - I’ve been holiday the last couple of weeks and have been pretty lax on keeping Ditto up to date with API changes recently (i.e. I haven’t been…)
I am testing a preliminary fix that just removes the private field from the transferred project (essentially resetting it to the default privacy, which appears to be private_to_team for my test workspace), but will update to use the privacy_setting field in the next day or two.
Apologies for the inconvenience,
Mike
3 Likes
Hi John,
Any advice on how I should detect the difference between a ‘private’ and ‘team private’ / ‘team shared’ project? I can’t tell any difference from the returned Project records in terms of team membership, etc.
The private_to_team privacy setting is not returned (just private) so I assume this value may have already been deprecated in favour of the sharing mechanism you mentioned, but I can’t see how to either view or change the sharing status via the API?
Here is a diff of two new projects created in the same team, one set to private and the other shared with the team:
Edit: reading [Change] Project team sharing is coming! - #4 by Phil_Seeman I see I will need to call the memberships endpoint to work this out.