🎯 The Challenge
You need to get the current user's email in a Model-Driven App. Sounds simple? There are multiple approaches, each with gotchas. Some work in dev but fail in production. Others return user IDs that break your API calls.
This guide shows you the reliable approach that works in enterprise environments.
📚 Table of Contents
🚀 The Production-Ready Solution
Here's the complete, battle-tested code that handles all edge cases and works in enterprise environments:
async function getCurrentUserEmail() {
try {
// Get current user ID from global context
const userId = Xrm.Utility.getGlobalContext().userSettings.userId;
// Clean user ID (remove curly braces if present)
const cleanUserId = userId.replace(/[{}]/g, "");
// Retrieve user email from systemuser table
const result = await Xrm.WebApi.retrieveRecord(
"systemuser",
cleanUserId,
"?$select=internalemailaddress,fullname"
);
return {
email: result.internalemailaddress,
name: result.fullname,
success: true
};
} catch (error) {
console.error('Error getting user email:', error);
// Fallback to basic user context
return {
success: false,
error: error.message,
fallback: Xrm.Utility.getGlobalContext().userSettings.userName
};
}
}
// Usage example
const userInfo = await getCurrentUserEmail();
if (userInfo.success) {
console.log('Email:', userInfo.email);
console.log('Name:', userInfo.name);
} else {
console.log('Fallback:', userInfo.fallback);
}
Why This Approach Works
This method uses Xrm.WebApi.retrieveRecord to get the actual email address from the user profile. It's reliable because:
✅ Key Advantages
- Returns real email addresses (not "DOMAIN\user")
- Works with enterprise security policies
- Handles permission errors gracefully
- Provides additional user details like full name
- Works consistently in development and production
- Includes proper error handling and fallbacks
📝 Practical Example: Auto-Fill Forms
Here's how to use it in real scenarios to auto-populate form fields with user information:
async function autoFillUserEmail(formContext) {
try {
// Show loading message
formContext.ui.setFormNotification(
'Loading your information...',
'INFO',
'loading'
);
// Get user information
const userInfo = await getCurrentUserEmail();
if (userInfo.success && userInfo.email) {
// Set email field
const emailField = formContext.getAttribute("emailaddress1");
if (emailField) {
emailField.setValue(userInfo.email);
}
// Set name field if available
const nameField = formContext.getAttribute("fullname");
if (nameField && userInfo.name) {
nameField.setValue(userInfo.name);
}
// Clear loading and show success
formContext.ui.clearFormNotification('loading');
formContext.ui.setFormNotification(
'Information loaded successfully!',
'INFO',
'success'
);
// Auto-clear success message
setTimeout(() => {
formContext.ui.clearFormNotification('success');
}, 3000);
}
} catch (error) {
formContext.ui.clearFormNotification('loading');
formContext.ui.setFormNotification(
'Could not load user information',
'WARNING',
'error'
);
console.error('Auto-fill error:', error);
}
}
Quick Method (With Limitations)
For simple cases, you can use the global context directly, but be aware of the limitations:
function getBasicUserInfo() {
const userSettings = Xrm.Utility.getGlobalContext().userSettings;
return {
userName: userSettings.userName, // Might be "domain\user"
userId: userSettings.userId,
// WARNING: userName might not be in email format!
potentialEmail: userSettings.userName
};
}
// Always validate the format
const info = getBasicUserInfo();
const isEmailFormat = /^[^\s@]+@[^\s@]+\.[^\s@]+$/.test(info.userName);
if (isEmailFormat) {
console.log('Email:', info.userName);
} else {
console.log('Not email format:', info.userName);
}
Important Limitation
In corporate environments, userName might return "COMPANY\johnsmith" instead of "john.smith@company.com". Always validate the format before using it as an email address.
🛡️ Bulletproof Implementation
For production applications, use this enhanced version that handles all edge cases and provides comprehensive fallbacks:
async function getReliableUserEmail() {
// Fallback data that always works
const fallbackData = {
source: 'global-context',
name: Xrm.Utility.getGlobalContext().userSettings.userName,
userId: Xrm.Utility.getGlobalContext().userSettings.userId,
email: null,
warning: 'Email not available - check permissions'
};
try {
// Try the API method first
const userInfo = await getCurrentUserEmail();
if (userInfo.success && userInfo.email) {
return {
source: 'api',
email: userInfo.email,
name: userInfo.name,
userId: fallbackData.userId,
success: true
};
}
// API worked but no email found
return {
...fallbackData,
warning: 'Email not set in user profile'
};
} catch (error) {
console.warn('API failed, using fallback:', error.message);
return fallbackData;
}
}
🎯 Key Takeaways
For Production Apps
Use Xrm.WebApi.retrieveRecord - it's reliable, secure, and returns real email addresses.
For Quick Prototypes
Global context is fine for testing, but always validate the format before using as email.
Always Have a Plan B
API calls can fail. Implement fallbacks so your app doesn't crash in production.
Clean Your Data
Remove curly braces from user IDs before making API calls to avoid errors.