Page 1681 "Email Logging Setup Wizard"

EmailLogging · Microsoft.CRM.EmailLoggin · captioned “Set Up Email Logging” · BC29-30 · source at ea08af5e · facts from BC29

Properties

Property	Value
Caption	Set Up Email Logging
PageType	NavigatePage
Permissions	tabledata “Email Logging Setup” = rimd

Fields on this page

Layout controls in source order, grouped by the container they sit in. Shows: the table field a control is bound to (or its expression as written); ToolTip: the control’s own, else the bound field’s (marked).

Group	Control	Shows	ToolTip
NotDoneBanner	NotDoneIcon	`MediaResourcesStandard."Media Reference"`	—
DoneBanner	DoneIcon	`MediaResourcesDone."Media Reference"`	—
Welcome to Email Logging Setup	LearnHowToSetupMailboxForEmailLogging	`LearnHowToSetupMailboxForEmailLoggingTxt`	—
	Manual setup done	`ManualSetupDone`	The settings in Exchange Online are complete.
Step2	ClientCredentialsLink	`ClientCredentialsLinkTxt`	—
SpecifiedCustomClientCredentialsGroup	Client ID and secret are specified and will be used to connect to the shared mailbox	`SpecifiedCustomClientCredentialsTxt`	Indicates that the client credentials are specified and will be used to connect to the shared mailbox.
ClientCredentialsRequiredGroup	ClientCredentialsRequired	`ClientCredentialsRequiredTxt`	Indicates that the client ID and secret are required to connect to the shared mailbox.
Step3	SignInAndGiveConsentLink	`SignInAndGiveConsentLinkTxt`	—
AdminSignInSucceed	SuccesfullyLoggedIn	`SuccesfullyLoggedInTxt`	Specifies if the Exchange administrator has logged in successfully.
AdminSignInFailed	UnsuccesfullyLoggedIn	`UnsuccesfullyLoggedInTxt`	Indicates that the Exchange Online administrator is not signed in.
Step3	Consent given	`AppConsentGiven`	Consent given
Step4	Shared Mailbox Email	`EmailAddress`	Specifies the email address of the shared mailbox. The shared mailbox must be in the same tenant as Business Central.
	ValidateMailboxLink	`ValidateMailboxLinkTxt`	—
ValidMailboxGroup	ValidMailbox	`ValidMailboxTxt`	The connection test was successful.
InvalidMailboxGroup	InvalidMailbox	`InvalidMailboxTxt`	The connection test was not successful.
	ErrorText	`ErrorText`	Specifies the error occurred.
AdvancedSection	Email Batch Size	`EmailBatchSize`	Specifies the number of email messages that the job queue entry for email logging will get from Exchange Online in one run. By balancing this number with how often the job queue entry runs you can fine tune the process. If a message is not logged in the current run it will be in the next one.
Control33	Create Email Logging Job Queue	`CreateEmailLoggingJobQueue`	Create Email Logging Job Queue
InvalidInteractionTemplateSetupGroup	InteractionTemplateSetupLink	`InteractionTemplateSetupLinkTxt`	—
	Interaction Template Setup needs to be configurred.	`InvalidInteractionTemplateSetupTxt`	Indicates that Interaction Template Setup needs to be configurred.
ValidInteractionTemplateSetupGroup	Interaction Template Setup is correctly configurred.	`ValidInteractionTemplateSetupTxt`	Indicates that Interaction Template Setup is correctly configurred.

Actions

Group	Action	ToolTip
Processing	Simple	—
	Advanced	—
	Back	Back
	Next	Next
	Finish	Finish

Procedures

10 local procedures, no public ones.

Triggers

OnInit, OnOpenPage, OnQueryClosePage

Calls

From the extracted call graph of BC29 (graphify-al on the snapshot checkout): calls whose target is known from a declared type or an Object::"Name" argument. Interface dispatch and calls through events are not counted, so the list is not complete.

Codeunit 1681 “Email Logging Management” (4 calls: OnInit → InitializeOAuthClient, ShowDoneStep → CheckInteractionTemplateSetup, SignInAndGiveAppConsent → ExtractTenantIdFromAccessToken, …)
Codeunit 1293 “Isolated Storage Management” (1 call: OnInit → Get)
Codeunit 1990 “Guided Experience” (1 call: OnQueryClosePage → AssistedSetupExistsAndIsNotComplete)
Codeunit 4030 “Client Type Management” (1 call: LoadTopBanners → GetCurrentClientType)
Codeunit 457 “Environment Information” (1 call: OnInit → IsSaaSInfrastructure)

Ask your agent

Procedure bodies are not stored here (D10). The call sections above are our own, per object, from the BC29 call graph. For a procedure body or the calls of one procedure, ask bc-code-atlas (external, by Stefan Maron, MIT; default corpus w1-28), which the bc-observatory plugin connects: bcatlas_resolve_node(object_type: "page", object_name: "Email Logging Setup Wizard"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.