Skip to content
New issue

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

Hash Key: Configurable TRIM #319

Open
MKloseINF opened this issue Feb 13, 2025 · 0 comments
Open

Hash Key: Configurable TRIM #319

MKloseINF opened this issue Feb 13, 2025 · 0 comments
Labels
enhancement New feature or request

Comments

@MKloseINF
Copy link

What additional value does this feature bring to the project?
Differentiate between business keys containing leading or trailing empty spaces

Is your feature request related to a problem? Please describe.
Business users can't report and identify figures for different business keys because they are mapped to one hash key

A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

We've incoming business keys e.g.
ABCDE
ABCDE
ABCDE
means empty space.
These are trimmed left and right to remove blanks.

Describe the solution you'd like
A variable where I can say trim TRUE or FALSE, similar to case sensitivity flag

A clear and concise description of what you want to happen.

Describe alternatives you've considered

A clear and concise description of any alternative solutions or features you've considered.

Additional context

We've on large customer side unfortunately business keys which are coming in with leading blanks which are removed while creating hash key. Our business users want to report and identify these values as different ones what is not possible with current solution.

@MKloseINF MKloseINF added the enhancement New feature or request label Feb 13, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant