Hey @OmarAlmonte ,
Reviewing the issue tracker for updates.
It’s been over 45 days and there’s been almost zero movement??
There are major, but ostensibly simple to implement gaps in the functionality dated back to January 16th that are still marked as “In Review”. I’m not talking about contentious or complex items like custom field filtering, but simple MVP functionality like reading/writing custom fields on anything other than a contact. Being unable to even read custom fields on various objects is a show stopper and we are dead in the water. We went all in on this migration to hit a March 10 date for starting the brownouts (which I know are on hold), but we are stuck hard due to the lack of movement from the API team.
Hi,
We understand the urgency. We’ve been making progress on the gaps, several have already been deployed, and others are in progress or under review as shown in the tracker.
We heard the community, and that’s why the brownouts have been postponed for now. This gives us additional time to close the remaining gaps. Our team is working hard to move these forward as quickly as possible.
We appreciate your patience and continued partnership.
Yes I understand about the postponement of the brownout. Thank you.
Why are major basic features still “In Review” 45+ days later?
What does “In Review” mean to you* guys? Haven’t made up your mind if you’re going to do it? Figuring out how to do it? My assumption (bad idea I know) was that it means you’re deciding whether or not to implement it at all.
Who looked at XMLRPC and REST v1 and the heat maps of which end points were in use and decided last year that REST v2 was “ready”?
Give that you were ready to start brown outs next week, and how huge the gap is even for remedial items, I am extremely concerned.
- The “royal” you of course, only addressed to you because you’re the poor soul stuck with talking to us evidently.