SDK NodeJS - loginEmail not available anymore

Beantwortet

Folgen

eDemo

• 31. Juli 2018 08:08

Hello,

From contact list, loginEmail is not defined anymore even if 2 users are in the same company and are in contact.

 

https://hub.openrainbow.com/#/documentation/doc/sdk/node/api/contact#Contact+loginEmail

 

 

Thanks

2

• Offizieller Kommentar

  

  Pascal BORSCHNECK

  • 1. August 2018 08:56

  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...

  Aktionen für Kommentare Permalink
• 

  Maxime LE MABEC

  • 31. Juli 2018 14:43

  "roles" field is also impacted.

  0

  Aktionen für Kommentare Permalink
• 

  eDemo

  • 1. August 2018 09:00

  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

  Aktionen für Kommentare Permalink
• 

  Pascal BORSCHNECK

  • 1. August 2018 11:28

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

  0

  Aktionen für Kommentare Permalink
• 

  Vincent BAILLEAU

  • 2. August 2018 08:21
  • Bearbeitet

  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

  Aktionen für Kommentare Permalink
• 

  eDemo

  • 2. August 2018 09:16

  Hello,

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

  Can you confirm?

  0

  Aktionen für Kommentare Permalink
• 

  Pascal BORSCHNECK

  • 2. August 2018 09:50

  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

  Aktionen für Kommentare Permalink

Bitte melden Sie sich an, um einen Kommentar zu hinterlassen.