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

Data type: Currency comma issue #4

Open
wissojr opened this issue Apr 9, 2019 · 5 comments
Open

Data type: Currency comma issue #4

wissojr opened this issue Apr 9, 2019 · 5 comments

Comments

@wissojr
Copy link

wissojr commented Apr 9, 2019

Hi @sfcure ,

We have found comma issue when you try to clone opportunity Field, where data type is example currency(16,2).

Example and Issue
If field (data type: currency(16.2)) original value is 150,45€ comma "moves" when cloning is done two times right. After clone field value is 15045,00€. It should be 150,45€

You can repeat this issue example if you create new custom field to opportunity form (use data type: currency(16,2)). Then try to change in cloning phase opportunity original field value example 100,45€ to another value example 150,45€ and then finish cloning phase. After clone opportunity value is in this example 15045,00€.

ps. Don't use zeroes on comma right side.

@sfcure
Copy link
Owner

sfcure commented May 3, 2019

@wissojr
I think it's a bug with lightning:recordForm as it does't work as expected in different locale numbers. I am investigating this and will update you soon.

@DerPapaBodo
Copy link

Calculated fields (e.g. Expected Revenue calculated with Amount * Probability) result in errors, when the calculation result has more than 2 numbers right of the comma.
e.g. 125,50€ * 25% = 30,125€ -> Error

Round currency seems to be buggy to.

P.S. Package is great!

@sfcure
Copy link
Owner

sfcure commented May 27, 2019

It's a bug with Lightning:RecordEditForm and to overcome this issue, I tried another approach but I am not able to create a package for this.

I have created another repository and you can use it for your use and update the code accordingly.

https://github.com/sfcure/CloneOppUnamanged

@wissojr
Copy link
Author

wissojr commented Jun 4, 2019

@sfcure Great work and thank you!
Why you aren't able to create package for this?
Do you have plan to implement this fix to main release?

@sfcure
Copy link
Owner

sfcure commented Jun 6, 2019

@wissojr - I will implement this fix into main release but I need to find a way where I can use the page-layout based on the record-type. This solution use a page-layout and doesn't use default layouts based on the record type.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants