If the account field is blank, the collection should just send a strongly worded email to the account owner and ask them to fill it in. Problem solved!
The EsaExchangeRetrieverService account permissions make sense if the account field is blank. Let's hope the service has the necessary access to the Exchange source.
Hmm, using the EsaApplicationService account permissions seems like a reasonable approach if the account field is blank. At least the collection can still run.
If the account field is blank, the collection should fail with an authentication error. How else would it verify the credentials to access the Exchange source?
Francoise
20 days agoWilda
22 days agoLashon
28 days agoFreeman
1 days agoNohemi
7 days agoLuis
1 months agoLisha
3 days agoVeda
1 months agoDomitila
1 months agoNadine
9 days agoFelix
26 days agoAnnette
28 days agoRicarda
2 months agoJospeh
2 months agoMozell
2 months agoDorethea
2 months agoMalcom
2 months agoPenney
2 months ago