Lawrence Duff

My feedback

  1. 20 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    4 comments  ·  Microsoft Planner - Feedback Forum » APIs  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Lawrence Duff commented  · 

    I'm trying to write a sync between Project Online and Planner tasks. Planner not having a last modified date/time makes that impossible without extra work detecting updates to Planner tasks with a trigger or similar and recording the date/time myself.

    Forgetting to include the last modified date/time in the API's to an app - only Microsoft could do that.

    Lawrence Duff supported this idea  · 
  2. 10,691 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    Hello! We wanted to provide an update to our status below. As we announced in our previous status update, our initial integration with To Do was our first step in a journey of bringing all your Microsoft Task Management services closer together, including Outlook and Planner. Through To Do, you can see your Planner tasks within Outlook on the Web.

    However, the continuing feedback on this post makes it clear that there is a desire for more work to be done to improve this experience. We want to make sure this feedback and votes aren’t getting lost by being added to this existing post.

    Instead, we’d like to make sure you have a forum to express these continuing pain points / desires, and a way to vote for which ones you’d like us to work on first (and how we should prioritize those asks against the many other great asks…

    An error occurred while saving the comment
    Lawrence Duff commented  · 

    The problem is MS don't have a consistent, repeatable, well thought out, design pattern for simple relational join implementations between their apps. A template that they could assert upon their app teams. They don't even implement CRUD fully in many single table type implementations: "You said in the user voice you wanted to add credit card details, you never said you wanted a delete or update function".

    Such literal requirements interpretation with no creative design thought leads only to the "Agile / Scrum mess".

    Every one-to-one, one-to-many, many-to-many join between different app data is another example. It's always a one off botch job. They might use guid's in the primary / foreign key relation or the labels (argh), it might be functionally complete filtering across the join, or it might not. Each join type connection implemented by an MS team "makes it up as they go along" with no design template, so each is uniquely incomplete and dysfunctional. By learning one you learn nothing about how the others might work, thereby lowering your productivity working cross app with MS. And since the integration join is incomplete and dysfunctional you always end on the Voice cox it doesn't work anyway. Should become a new phrase we can use instead of more pejorative terms - "I just spent two days trying to do such and such, but no, I just discovered I've been *Voiced* by Microsoft".

    Lawrence Duff supported this idea  · 

Feedback and Knowledge Base