Add example for field calculateion map #2750
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.
This pull request introduces a new
FieldCalculationMapfeature to the field mapping tool, enabling dynamic calculations for fields based on custom expressions and parameters. It also updates documentation and enhances code logic to support this feature.Feature Implementation:
FieldCalculationMapFieldCalculationMap, inappsettings.json. This allows calculations like[effort] * [rate]using parameters (effortandrate) and maps the result to a target field (Custom.EstimatedCost). [1] [2]Documentation Updates
reference.fieldmaps.fieldcalculationmap.yamlandreference.tools.fieldmappingtool.yamlto include examples and samples for theFieldCalculationMapconfiguration. [1] [2] [3]reference.fieldmaps.fieldcalculationmap.mdandreference.tools.fieldmappingtool.mdto provide detailed code samples and descriptions for the new mapping type. [1] [2] [3]Code Logic Enhancement
ConvertSectionWithPathToJsoninClassDataLoader.csto ensureObjectNameandOptionForproperties are added only if they are missing in the JSON object. This prevents redundant additions and ensures cleaner data handling.