ODMAD: Read objects are missing attributes despite them being present (4381311)

In ODMAD, attributes are missing from objects after a Read operation, even though they exist in the source. For example, when reading an Entra-joined device from a cloud environment, attributes such as sAMAccountName or DeviceID may not be populated. Similar behavior can also occur in on-premises environments.

Additionally, when reviewing Environment Settings → Used Attributes, the required attributes are not listed, despite being expected.

The issue occurs due to the absence of default templates at the time the environment is added.

This situation can arise when attempting to reuse an environment that was originally created as part of a Domain Rewrite project, where the default templates were not provisioned.

To resolve the issue, follow these steps:

1. Navigate to Menu → Templates and create a new template, keeping all default settings.

   • Ensure that the template uses the same source and target types as the affected environment.
   • Verify that the missing attribute is included in the template mappings.

2. Create a new workflow and remove all modules except for the Stage module.

3. Configure the Stage module to use the newly created template.

4. Run the workflow with the Read action against the affected environment.

   • Important: Do not run the workflow with the Stage configuration that was previously created.

5. Navigate to Menu → Environments, select the affected environment, and open Used Attributes.

   • Confirm that the previously missing attribute now appears in the list.

Note:
In some cases, it may be necessary to re-read the affected objects (AD or Entra). To do this:

• Remove the objects from the scope
• Run a Read on the environment using the Reconcile option
• Add the objects back into scope
• Run the Read again