-
Notifications
You must be signed in to change notification settings - Fork 209
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Only 50 subscriptions retreived #85
Comments
I am trying the changes related to manage tenant to see if that fixes this. will reopen otherwise. |
ok - still have this issue, only 50 subscriptions are being retrieved from the api call; meaning that for all of the data tables, only the first 50 subscription are queried and populated. I had tried to modify all subscriptions table, but discovered that rather than each table build, build from that table, they all make the same query. Any ideas how I can fix? |
actually we have dashboards with hundreds of subscriptions working. So the 50 subscriptions limitation issue is new. We might need to see the exact error with the PBIX file. can you share an email and we will reach out to you? |
colin [dot] bradford @ blueprism [dot] com |
Taking your issue offline for now until we identify if its a unique issue for your environment. Will post the resolution later on after working with you remotely |
We detected during the troubleshooting session with @CeeeBeee that sometimes the Subscriptions API returns only the first 50 subscriptions and the nextlink field. We're currently adapting the dashboard to receive all the subscriptions. |
Many thanks.
Best Regards
COLIN BRADFORD
BluePrismCloud COO
e: colin.bradford@blueprism.com
t: +44 7545374611
…________________________________
From: Jordi Suñé <notifications@github.com>
Sent: Tuesday, April 21, 2020 8:42:35 PM
To: Azure/ccodashboard <ccodashboard@noreply.github.com>
Cc: Colin Bradford <colin.bradford@blueprism.com>; Mention <mention@noreply.github.com>
Subject: Re: [Azure/ccodashboard] Only 50 subscriptions retreived (#85)
Closed #85 . — You are receiving this because you were mentioned. Reply to thi
Email scanned - Sender unknown | CORVID Email Protection<https://corvid.it/cyber-solutions/email-protection/>
⚠ Replying may not go to displayed sender
View email info<https://pernixconsole.corvid.it/emaildetailbrief/405CECBC-8408-11EA-80A2-3721971E80B0> | View all emails<https://pernixconsole.corvid.it/genotl> | Report as suspicious<mailto:pernixsus@ultra-cpg.com?subject=Reporting%20Suspicious%20Pernix%20Email&body=The%20email%20405CECBC-8408-11EA-80A2-3721971E80B0%20is%20suspicious> | Sender: [noreply@github.com]
Closed #85<#85>.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub<#85 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/APCRRVMSETRIL3FIDGB54O3RNXZKXANCNFSM4MDAIOPQ>.
This e-mail from Blue Prism Group plc or a member of its group of companies is intended exclusively for the addressee and may contain legally privileged or confidential information. If you are not the intended recipient you must not read use nor disclose the information in the email or attachments. Please notify Blue Prism by replying to this email and permanently delete the email from your records. Blue Prism operates an anti-virus policy but does not accept responsibility for any damage caused by viruses transmitted. Blue Prism Group plc Registered in England No: 09759493. Registered Office: 2 Cinnamon Park, Warrington, Cheshire, WA2 0XP
|
Hi,
I have over 180 subscriptions, it appears that the management.azure.com/subscriptions API call is only retrieving 50 subscriptions. So I have extracted using powershell the full subscription list, and appended it into the AllSubscription table. However, when I refresh, whilst the number of subscriptions increases, the resources groups, virtual machines etc are not pulled from the full list of subscriptions in the AllSubscription table.
Is this expected behaviour? or can you advise how this could be resolved please.
Thanks
Colin
The text was updated successfully, but these errors were encountered: