Int32 error when using Yammer Get Groups on External Networks

[Anonymous]

Hi there,

I have two new tenants that I've created on which I need to run a Flow that will use the "Get Groups" Yammer action, before carrying out other stages. I'm finding that when using this action, and selecting the drop-down to choose an External Network, I get the following error:

"Could not retrieve values. Value was either too large or too small for an Int32. at System.Convert.ToInt32(Int64 value) at System.Convert.ChangeType(Object value, Type conversionType, IFormatProvider provider) at Newtonsoft.Json.Linq.Extensions.Convert[T,U](T token) at Newtonsoft.Json.Linq.JToken.Value[T](Object key)"

I've checked all settings I can think of, including enabling the use of third party applications, but cannot work out why this won't work to select external networks. On our live internal tenant it works perfectly, though. Just not on these two new tenants.

Has anyone else seen this, and if so, do you know how I can resolve the issue?

Thanks very much in advance for any assistance you can offer.

Alex

[v-yamao-msft]

Hi @Anonymous ,

Thanks for feedback.

The issue could be reproduced by me. When clicking the drop down to choose an External Network, the error message you’ve mentioned will be returned.

As far as I know, there was a limitation of Yammer connector that when you consent a Yammer connection with your credentials, it grants access only to the primary network. The connector doesn’t support getting access to external networks.

I will help confirm this issue and back to you later.

Best regards,

Mabel

[Anonymous]

Hi Mabel,

The thing is, it does work for me on another tenant. I've spent some time trying to find differences between the two and what I've found is the only difference is the URL in which I'm accessing Flow. On the tenant where the function works (and resolves external networks) it's running from "emea.flow.microsoft.com" and on the tenant where it doesn't work it is using "unitedkingdom.flow.microsoft.com". Could that have something to do with it, do you think?

[v-yamao-msft]

Hi @Anonymous ,

Do you mean that under tenant from “emea.flow.microsoft.com”, external networks are working properly?

Could you share the flow URLs of the working and not working flow under different tenant?

Best regards,

Mabel

[Anonymous]

I am also getting this error and I believe it is a coding bug.

An int32 can only go up to 2,147,483,647 and the group I was trying to work with was 2,327,216,128

Code change to leave it as int64?

[Anonymous · Accepted solution]

We had the same suspicion on this end too. After reporting it to Microsoft they have since implemented a fix, which thankfully has the situation resolved and my Flows work as intended! 🙂