Comments
I found this thread while searching for the Purchase Line Review Page. This should be be enabled for price pages, not just sales. My client wishes for the ability to change the Starting and Ending date, and create a new line from the filtered list. This worked before the new pricing experience.
For our business case, we have locations for damaged goods and QA inspection. These can usually be handled by managing the inventory status, but if an employee forgets to set the inventory status, we can run into serious problems reserving damaged goods for orders. Batch jobs wont work due to the frequency of operations at our company.
There was a lively discussion about this on Yammer (https://www.yammer.com/dynamicsnavdev/#/Threads/show?threadId=3039600681410560). Thanks to the helpful input from the Business Central community, it seems this idea is no longer necessary and can be closed. It turns out that there is a PowerShell cmdlet that enables this functionality for shared mailboxes. To implement it, you need to add the “Send As” permission to the shared mailbox in the Exchange Admin Center. However, this option isn’t available directly in the Exchange Admin Center interface. Instead, you need to connect to Exchange Online via PowerShell and enable the MessageCopyForSentAsEnabled setting for the shared mailbox (for example, invoices@contoso.com):Set-Mailbox invoices@contoso.com -MessageCopyForSentAsEnabled $trueFor more details, see the documentation: https://learn.microsoft.com/en-us/exchange/recipients-in-exchange-online/manage-user-mailboxes/automatically-save-sent-items-in-delegator-s-mailbox#how-do-i-set-up-a-mailbox-to-save-messages-sent-as-a-manager-when-theyre-sent-by-an-assistant
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".
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.
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.