Feature/nickname and reference #27
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…icknames and reference ids to drive the connection of look up references within recipes
…key or based off nickname using expected underscore split convention
jdschleicher
added a commit
that referenced
this pull request
Jul 5, 2025
#27 (#28) * feat: concating nickname and unique reference id to allow for using nicknames and reference ids to drive the connection of look up references within recipes * feat: replacement of reference values that may be incremental record key or based off nickname using expected underscore split convention * docs: initial change log adjustments for new feature * docs: change log update with example of nickname usage * build: incrementing minor version number * docs: update to pull request template to remember version update
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Motivation and Context
When creating data recipes that are intended to be created an a target org, we need the ability to be able to create relationships between objects. This functionality is available using an convention of "Account_Reference_1" but this functionality is not documented and is a blind-faith approach to creating relationships between a child object and a parent object.
With this update we can now leverage the yaml property "nickname" on a parent object. When a child object needs to reference a parent to populate for a lookup or masterdetail field, it can provide the nickname as its value:
Any Technical Decisions to Note??
Introduced a convention when creating reference keys that will allow for pointing lookup fields to expected parent record ids using nickname or the incremental reference record ( "Account_Reference_1" )
Type of Change
How Has This Been Tested?
Test Details
[Describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration]
Checklist
Changelog for branch: feature/nicknameAndReference
Generated on: 2025-07-04
Summary
Changes at a glance
Added Files
Modified Files
Deleted Files
Renamed Files