Feat(multientities): use organizations default_currency and timezone from the default billing_entity #3547
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
annvelents
commented
Apr 28, 2025
Base automatically changed from
feat/multientities-6-update-invoice_net_term
to
main
May 13, 2025 07:44
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.
Context
Since we're deprecating these fields on organization, we should be taking them from the default billing_entity when sending to the frontend.
The analytics still should collect data for different currencies, but on the FE they're sending us default currency of org to filter the values
Description
Redefined default_currency and timezone on org
changed the way we retrieve default_billing_entity to not have to reload the association