Home
%3CLINGO-SUB%20id%3D%22lingo-sub-334670%22%20slang%3D%22en-US%22%3ESome%20Yammer%20IDs%20returned%20by%20the%20REST%20API%20have%20grown%20beyond%2032%20bits%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-334670%22%20slang%3D%22en-US%22%3E%3CP%3EIt%20has%20come%20to%20our%20attention%20that%20some%20customer%20and%20partner%20apps%20that%20have%20been%20developed%20against%20our%20API%20have%20expected%20Yammer%20IDs%20to%20be%2032%20bit.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThe%20Yammer%20REST%20API%20exposes%20a%20number%20of%20IDs%20of%20various%20objects%20inside%20Yammer%20including%20MessageID%2C%20UserID%2C%20GroupID%2C%20etc.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThese%20IDs%20are%20not%2032%20bit%20in%20Yammer%2C%20and%20some%20now%20have%20moved%20beyond%20the%20amount%20of%20memory%20storable%20by%2032%20bits.%26nbsp%3B%20%26nbsp%3BAs%20exposed%20by%20our%20Yammer%20API%20Yammer%20IDs%20are%20JSON%20integers%20which%20at%20the%20time%20of%20this%20posting%20allow%20up%20to%2053%20bits.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3ERestricting%20your%20variables%20that%20contain%20Yammer%20IDs%20to%20be%2032%20bit%20integers%20will%20cause%20your%20apps%20to%20be%20unreliable%20at%20best%2C%20and%20most%20likely%20they%20will%20crash.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-TEASER%20id%3D%22lingo-teaser-334670%22%20slang%3D%22en-US%22%3E%3CP%3EIt%20has%20come%20to%20our%20attention%20that%20some%20customer%20and%20partner%20apps%20that%20have%20been%20developed%20against%20our%20API%20have%20expected%20the%20IDs%20to%20be%2032%20bit.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-TEASER%3E%3CLINGO-SUB%20id%3D%22lingo-sub-376784%22%20slang%3D%22en-US%22%3ERe%3A%20Some%20Yammer%20IDs%20returned%20by%20the%20REST%20API%20have%20grown%20beyond%2032%20bits%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-376784%22%20slang%3D%22en-US%22%3E%3CP%3ECan%20you%20please%20check%20and%20tell%20if%20any%20possible%20impact%20on%20our%20SPO%20site%20as%20we%20are%20using%20OOTB%20Yammer%20feed%20using%20javascript%20inside%20a%20script%20editor.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThere%20is%20the%20following%20Message%20in%20O365%20Admin%20Center%2C%20which%20may%20(but%20doesn%E2%80%99t%20have%20to)%20have%20an%20impact%20on%20our%20site%2C%20which%20I%20think%20integrates%20with%20Yammer%20groups.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe're%20making%20some%20changes%20to%20Yammer%20IDs%20that%20are%20exposed%20in%20our%20Yammer%20APIs.%20On%20April%204%2C%202019%20some%20of%20our%20Yammer%20IDs%20may%20grow%20beyond%2032%20bits%20in%20size.%20This%20change%20does%20not%20impact%20Office%20365%20subscriptions%20in%20GCC.%20%5BHow%20does%20this%20impact%20me%3F%5D%20You%20are%20receiving%20this%20message%20because%20it%20is%20possible%20that%20you%20have%20custom%20Yammer%20applications%20that%20consume%20Yammer%20IDs%20and%20you%20should%20know%20that%20if%20they%20are%20storing%20them%20as%2032-bit%20integers%20they%20could%20start%20to%20fail.%20If%20your%20custom%20apps%20are%20built%20by%20third-party%20app%20developers%2C%20you%20should%20contact%20them%20to%20make%20sure%20they%20update%20their%20apps%20accordingly.%20If%20you%20do%20not%20have%20custom%20Yammer%20applications%20you%20can%20disregard%20this%20message.%20%5BWhat%20should%20I%20do%20to%20prepare%20for%20this%20change%3F%5D%20When%20this%20change%20takes%20effect%2C%20you%20will%20need%20to%20have%20modified%20your%20custom%20Yammer%20applications%20to%20not%20restrict%20Yammer%20ID%20variables%20to%2032%20bits.%20Please%20click%20Additional%20Information%20to%20learn%20more.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESome%20Yammer%20IDs%20returned%20by%20the%20REST%20API%20have%20grown%20beyond%2032%20bits%3C%2FP%3E%3CP%3EIt%20has%20come%20to%20our%20attention%20that%20some%20customer%20and%20partner%20apps%20that%20have%20been%20developed%20against%20our%20API%20have%20expected%20Yammer%20IDs%20to%20be%2032%20bit.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20Yammer%20REST%20API%20exposes%20a%20number%20of%20IDs%20of%20various%20objects%20inside%20Yammer%20including%20MessageID%2C%20UserID%2C%20GroupID%2C%20etc.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThese%20IDs%20are%20not%2032%20bit%20in%20Yammer%2C%20and%20some%20now%20have%20moved%20beyond%20the%20amount%20of%20memory%20storable%20by%2032%20bits.%26nbsp%3B%20%26nbsp%3BAs%20exposed%20by%20our%20Yammer%20API%20Yammer%20IDs%20are%20JSON%20integers%20which%20at%20the%20time%20of%20this%20posting%20allow%20up%20to%2053%20bits.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ERestricting%20your%20variables%20that%20contain%20Yammer%20IDs%20to%20be%2032%20bit%20integers%20will%20cause%20your%20apps%20to%20be%20unreliable%20at%20best%2C%20and%20most%20likely%20they%20will%20crash.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-366839%22%20slang%3D%22en-US%22%3ERe%3A%20Some%20Yammer%20IDs%20returned%20by%20the%20REST%20API%20have%20grown%20beyond%2032%20bits%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-366839%22%20slang%3D%22en-US%22%3E%3CBLOCKQUOTE%3E%3CP%3E%3CSPAN%3EThese%20IDs%20are%20not%2032%20bit%20in%20Yammer%2C%20and%20%3CU%3Esome%20now%20have%20moved%20beyond%3C%2FU%3E%20the%20amount%20of%20memory%20storable%20by%2032%20bits.%3C%2FSPAN%3E%3C%2FP%3E%3C%2FBLOCKQUOTE%3E%3CP%3E%3CSPAN%3EAre%20you%20able%20to%20provide%20specific%20detail%20about%20GroupID%3F%20We%20need%20to%20understand%20the%20urgency%20of%20the%20change%20in%20our%20app.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EIf%20it%20is%20generated%20sequentially%2C%20I%20believe%20GroupID%20requires%20about%2025%20bits%20at%20the%20moment.%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-665368%22%20slang%3D%22en-US%22%3ERe%3A%20Some%20Yammer%20IDs%20returned%20by%20the%20REST%20API%20have%20grown%20beyond%2032%20bits%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-665368%22%20slang%3D%22en-US%22%3E%3CP%3EJust%20ran%20into%20this%20today.%20Our%20Yammer%20users%20that%20I%20interact%20with%20via%20the%20API%20have%20newer%20ID's%20that%20exceed%20the%2032-bit%20maximum%20integer%20value.%20I%20am%20a%20contributor%20to%20a%20GitHub%20project%20(%3CA%20href%3D%22https%3A%2F%2Fgithub.com%2FRaynaldM%2FYammer.SimpleAPI%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fgithub.com%2FRaynaldM%2FYammer.SimpleAPI%3C%2FA%3E)%20that%20serves%20as%20a%20Yammer%20API%20wrapper.%20Just%20committed%20the%20change%20of%20all%20int%20ID%20references%20to%20be%20long%20data%20types.%20Works%20like%20a%20charm%20again.%20It%20would've%20been%20nice%20if%20there%20was%20some%20announcement%20of%20this.%20If%20there%20was%20anything%20I%20wasn't%20in%20the%20loop!%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EUPDATE%3A%20I%20re-read%20some%20older%20Office%20365%20Message%20Center%20digests.%20The%20one%20from%203%2F11%2F2019%20listed%20MC175309%2C%20describing%20this%20impacting%20change.%20My%20mistake%20for%20not%20reading%20these%20carefully%20enough.%26nbsp%3B%3Asmileyhappy%3A%3C%2FP%3E%3C%2FLINGO-BODY%3E
Microsoft

It has come to our attention that some customer and partner apps that have been developed against our API have expected Yammer IDs to be 32 bit.

 

The Yammer REST API exposes a number of IDs of various objects inside Yammer including MessageID, UserID, GroupID, etc.

 

These IDs are not 32 bit in Yammer, and some now have moved beyond the amount of memory storable by 32 bits.   As exposed by our Yammer API Yammer IDs are JSON integers which at the time of this posting allow up to 53 bits.

 

Restricting your variables that contain Yammer IDs to be 32 bit integers will cause your apps to be unreliable at best, and most likely they will crash.

3 Comments
Occasional Visitor

These IDs are not 32 bit in Yammer, and some now have moved beyond the amount of memory storable by 32 bits.

Are you able to provide specific detail about GroupID? We need to understand the urgency of the change in our app.

 

If it is generated sequentially, I believe GroupID requires about 25 bits at the moment.

Frequent Visitor

Can you please check and tell if any possible impact on our SPO site as we are using OOTB Yammer feed using javascript inside a script editor.

 

 

There is the following Message in O365 Admin Center, which may (but doesn’t have to) have an impact on our site, which I think integrates with Yammer groups.

 

We're making some changes to Yammer IDs that are exposed in our Yammer APIs. On April 4, 2019 some of our Yammer IDs may grow beyond 32 bits in size. This change does not impact Office 365 subscriptions in GCC. [How does this impact me?] You are receiving this message because it is possible that you have custom Yammer applications that consume Yammer IDs and you should know that if they are storing them as 32-bit integers they could start to fail. If your custom apps are built by third-party app developers, you should contact them to make sure they update their apps accordingly. If you do not have custom Yammer applications you can disregard this message. [What should I do to prepare for this change?] When this change takes effect, you will need to have modified your custom Yammer applications to not restrict Yammer ID variables to 32 bits. Please click Additional Information to learn more.

 

Some Yammer IDs returned by the REST API have grown beyond 32 bits

It has come to our attention that some customer and partner apps that have been developed against our API have expected Yammer IDs to be 32 bit.

 

The Yammer REST API exposes a number of IDs of various objects inside Yammer including MessageID, UserID, GroupID, etc.

 

These IDs are not 32 bit in Yammer, and some now have moved beyond the amount of memory storable by 32 bits.   As exposed by our Yammer API Yammer IDs are JSON integers which at the time of this posting allow up to 53 bits.

 

Restricting your variables that contain Yammer IDs to be 32 bit integers will cause your apps to be unreliable at best, and most likely they will crash.

Occasional Visitor

Just ran into this today. Our Yammer users that I interact with via the API have newer ID's that exceed the 32-bit maximum integer value. I am a contributor to a GitHub project (https://github.com/RaynaldM/Yammer.SimpleAPI) that serves as a Yammer API wrapper. Just committed the change of all int ID references to be long data types. Works like a charm again. It would've been nice if there was some announcement of this. If there was anything I wasn't in the loop!

 

UPDATE: I re-read some older Office 365 Message Center digests. The one from 3/11/2019 listed MC175309, describing this impacting change. My mistake for not reading these carefully enough. :smileyhappy: