Added support for display name in DataProperty and NavigationProperty #23
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
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.
Hi,
I found some hints in the internet (stackoverflow & co) that in order to have the %displayName% replaced in the validation messages with a proper display name, one should set the displayName field in the DataProperty. I thought that this information could be sent from the server anyway, so why not include it in the metadata already. I did this on my test machine and it works pretty well. I was wondering, though, if we could also send custom metadata from server, like field description and watermark. I understand that this is custom code, but it could be very helpful to allow also setting such fields.
Regards,
Ioan