Fix Invalid Lookups of namespaced fields #3759
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
W-15157537
These modifications address the error reported in Issue #3752.
The issue stemmed from the fact that during loading, when namespaces were injected into the mapping, only the key of the lookups dictionary would be altered, not the lookup class itself. For instance,
mapping.lookups
would appear as follows:In the
_infer_and_validate_lookups
function withinmapping_parser.py
, we validate whether the sObjects mentioned in the mapping file under the lookup field are indeed part of thereferenceTo
of that field. However, the problem arose from the utilization of thename
attribute underMappingLookup
instead of the key value.Change: We've modified it to reference the
name
with the key value ofmapping.lookups
instead of accessing it withinMappingLookup
class. This way thename
would be the field with the injected namespaceFixes #3752