Better Export for Custom Fields #103
Open
Conversation
This file contains 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
I have added custom fields to SSLP via a custom plugin. For some reason, when I export the data the custom fields are out of order. (For example, I would have phone numbers showing in the Bio column on the csv.) If you write the custom data by directly referencing the key name (probably not saying that right) rather than looping through each key -> value pair, I can force the export to retain the correct order. Not sure if that is useful to anyone else, but it works for me. Until there is support for custom fields in this plug in.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
I have added custom fields to SSLP via a custom plugin. For some reason, when I export the data the custom fields are out of order. (For example, I would have phone numbers showing in the Bio column on the csv.) If you write the custom data by directly referencing the key name (probably not saying that right) rather than looping through each key -> value pair, I can force the export to retain the correct order.
Not sure if that is useful to anyone else, but it works for me. Until there is support for custom fields in this plug in.