We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
We have hit an issue in the report runner where we have parameter values that require a leading space and an optional trailing space.
The current implementation does not support this functionality since it is calling trim on the ParameterValue in the ParameterCore.cs file.
We can easily remove the .trim() function for our purposes but a parameter flag of -T On|Off would be beneficial in this case.
The text was updated successfully, but these errors were encountered:
The Trim function has been removed by mikecrf121 in a fork he made of my repo. https://github.com/mhertzfeld/CrystalReportsNinja/commits?author=mikecrf121
I have merged mikecrf121's change into my repo. You can test the change in the following branch of my repo. https://github.com/mhertzfeld/CrystalReportsNinja/tree/1.4.0.0
If you still would like a parameter added for this functionality you can create an issue under my repo and I will look into addressing it.
https://github.com/mhertzfeld/CrystalReportsNinja/issues
Sorry, something went wrong.
Merge pull request rainforestnet#42 from danielleevandenbosch/patch-1
9acaf6a
Removed extra instance of CSV in the readme file.
No branches or pull requests
We have hit an issue in the report runner where we have parameter values that require a leading space and an optional trailing space.
The current implementation does not support this functionality since it is calling trim on the ParameterValue in the ParameterCore.cs file.
We can easily remove the .trim() function for our purposes but a parameter flag of -T On|Off would be beneficial in this case.
The text was updated successfully, but these errors were encountered: