Top

Comments

7 comments

  • Official comment
    Pascal BORSCHNECK

    Hi and thanks.

    We are aware of the problem.  It's a side effect of GPRD and we are working on this with Legals, Architects and so on...

    Comment actions Permalink
  • Maxime LE MABEC

    "roles" field is also impacted.

    0
    Comment actions Permalink
  • eDemo

    Thanks for the answer Pascal.

    Can we expect a rollback for few sprints, to let time for developers (especially during vacation period) to adapt their development?

    0
    Comment actions Permalink
  • Pascal BORSCHNECK

    I am waiting for replies, I can't say for the moment what/how/when.

    0
    Comment actions Permalink
  • Vincent BAILLEAU

    Hi,

    A rollback on loginEmail as been done yesterday. In the next month, following the 3 Release Breaking Changing, the field loginEmail have be removed form Contact object again. In the meantime we will propose an alternative.

    As company admin LoginEmail stay readable. In order to identify contacts you may also use the "emails[]" collection.

    0
    Comment actions Permalink
  • eDemo

    Hello,

    It looks that the rollback is only applicable for users but not for groups (group.users.loginEmail)

    Can you confirm?

    0
    Comment actions Permalink
  • Pascal BORSCHNECK

    I checked with server's team and confirm.  No loginEmail rollback for groups for the moment.

     

    It'll be done but with following limitation: in server's reply you'll just see loginEmail from the users in YOUR COMPANY.
    If public user and/or user in your roster but not in your company: it'll be empty.

     

    0
    Comment actions Permalink

Please sign in to leave a comment.

Still can't find what you need?

  • Contact Us

    Do you have any question about Rainbow? Leave us a message to get more information.

    Contact
  • Ask the Community

    Do you need help? Ask your questions to the Community and get answers from other Rainbow users.

    Post message