on
RE:
Apologies for the duplicate comment.The text did not display as I intended after I clicked Submit.Briefly: From my perspective, access to token expiration information is essential, so codeunits like codeunit 560 "CrossIntercompany Connector" in "Base Application W1-25" should avoid using constants like StandardExpirationInSeconds := 3599 to store "Token Expiration Time".
RE:
When the warning `"AL0432: Method 'AcquireTokenWithClientCredentials' is marked for removal. Reason: Use AcquireTokenWithClientCredentials with SecretText data type for AccessToken.. Tag: 24.0."` appears, I notice that I can no longer retrieve information about token expiration.Searching within "Base Application w1-25," I found an example in Codeunit 560, **CrossIntercompany Connector**, where expiration is handled using a constant `StandardExpirationInSeconds := 3599`.```al internal procedure GetBearerAccessToken(var ICPartner: Record "IC Partner"): SecretText var Token: SecretText; begin if (ICPartner."Token Expiration Time" Token := AcquireBearerAccessToken(ICPartner); if StoreTokenInICPartner then begin ICPartner.SetSecret(ICPartner."Token Key", Token); ICPartner."Token Expiration Time" := CurrentDateTime + StandardExpirationInSeconds; // StandardExpirationInSeconds is a constant. ICPartner.Modify(); end end else Token := ICPartner.GetSecret(ICPartner."Token Key"); exit(Token); end;```I'm concerned about cache issues when changing App registration because the `OAuth2` Codeunit, as I recently discovered, manages expiration internally. Knowing access token details and expiration time feels essential from my perspective.
RE:
When the warning `"AL0432: Method 'AcquireTokenWithClientCredentials' is marked for removal. Reason: Use AcquireTokenWithClientCredentials with SecretText data type for AccessToken.. Tag: 24.0."` appears, I notice that I can no longer retrieve information about token expiration.Searching within "Base Application w1-25," I found an example in Codeunit 560, **CrossIntercompany Connector**, where expiration is handled using a constant `StandardExpirationInSeconds := 3599`.```al internal procedure GetBearerAccessToken(var ICPartner: Record "IC Partner"): SecretText var Token: SecretText; begin if (ICPartner."Token Expiration Time" Token := AcquireBearerAccessToken(ICPartner); if StoreTokenInICPartner then begin ICPartner.SetSecret(ICPartner."Token Key", Token); ICPartner."Token Expiration Time" := CurrentDateTime + StandardExpirationInSeconds; // StandardExpirationInSeconds is a constant. ICPartner.Modify(); end end else Token := ICPartner.GetSecret(ICPartner."Token Key"); exit(Token); end;```I'm concerned about cache issues when changing App registration because the `OAuth2` Codeunit, as I recently discovered, manages expiration internally. Knowing access token expiration time feels essential from my perspective.
RE:
Dashboards with a lot of indicators need this feature. Please implement
RE:
USERCULTURE() returns almost what Power Bi report developers need here. Except this does not have the info of timezone or the user timezone offset from UTC.To get the current time zone offset in JavaScript, you can use the getTimezoneOffset() method of the Date object. This method returns the time zone offset in minutes from UTC for the current locale. But as Power Bi can not access resources on the local computer, I would suggest Microsoft to implement something like a USERUTCTIMEOFFSET()function in the same way it can show the USERCULTURE that then can be used in DAX to determine time difference.This can be very useful when reports are used around the world - that works interactive with live data - and displayed to user according to local time. (Otherwise any time stamps in data is useless to include.)
RE:
https://learn.microsoft.com/en-us/power-platform/admin/enable-use-comprehensive-auditing#review-your-audit-data-using-reports-in-microsoft-purview-compliance-portal
RE:
This feature is essential for Dynamics 365 / Power Platform.
RE:
Large companies often have many datasets in direct query due to the need to always have up-to-date data for decision making. In some cases, stored procedures can be an important resource to improve query performance.
RE:
I also would like a way to be able to manage credentials for various data sources used across Fabric within a given Workspace. I cannot always use a service principal or a generated workspace identity with some of my data sources.
RE:
Anything new on this one? Seems strange that its not possible in 2024 to add and use Web fonts by importing them in the jason Theme or something.