Details
-
Type:
Bug
-
Status: Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 3.0.0
-
Fix Version/s: 3.3.0-b1
-
Component/s: None
-
Labels:None
Description
If a client has no tax_id setting set, because of the setting inheritance in Blesta, the company's tax_id is set in place of the client's tax_id.
This generally only occurs when a client is added via importation or API.
The solution therefore, should be to rename the company tax_id so as to prevent inheritance, or to somehow ensure that a client tax_id is always set (even if blank).
Issue Links
- is blocked by
-
CORE-1111
Add option to not inherit company setting
-
- Closed
-
Activity
Cody Phillips (Inactive)
created issue -
Yes, but it is not an issue with the migrator so much as it is a design flaw with Blesta. The two settings are named exactly the same, but serve separate purposes. There should be no inheritance between the two.
Cody Phillips (Inactive)
added a comment - Yes, but it is not an issue with the migrator so much as it is a design flaw with Blesta. The two settings are named exactly the same, but serve separate purposes. There should be no inheritance between the two. 
Paul Phillips
made changes -
| Field | Original Value | New Value |
|---|---|---|
| Fix Version/s | 3.1.3 [ 10405 ] | |
| Fix Version/s | 3.1.2 [ 10403 ] |
Cody Phillips (Inactive)
made changes -
| Summary | Company tax_id inherited when not client tax_id set | Company tax_id inherited when no client tax_id set |
Cody Phillips (Inactive)
made changes -
Paul Phillips
made changes -
| Fix Version/s | 3.1.4 [ 10500 ] | |
| Fix Version/s | 3.1.3 [ 10405 ] |
Paul Phillips
made changes -
| Fix Version/s | 3.2.0-b2 [ 10501 ] | |
| Fix Version/s | 3.2.0-b1 [ 10002 ] |
Paul Phillips
made changes -
| Fix Version/s | 3.2.0-b3 [ 10503 ] | |
| Fix Version/s | 3.2.0-b2 [ 10501 ] |
Cody Phillips (Inactive)
made changes -
| Fix Version/s | 3.3.0 [ 10100 ] | |
| Fix Version/s | 3.1.4 [ 10500 ] | |
| Fix Version/s | 3.2.0-b3 [ 10503 ] |
Cody Phillips (Inactive)
made changes -
| Fix Version/s | 3.2.0-b3 [ 10503 ] | |
| Fix Version/s | 3.3.0 [ 10100 ] |
Paul Phillips
made changes -
| Fix Version/s | 3.2.0 [ 10502 ] | |
| Fix Version/s | 3.2.0-b3 [ 10503 ] |
Paul Phillips
made changes -
| Fix Version/s | 3.3.0 [ 10100 ] | |
| Fix Version/s | 3.2.0 [ 10502 ] |
Tyson Phillips (Inactive)
made changes -
| Assignee | Cody Phillips [ cody ] | Tyson Phillips [ tyson ] |
CORE-1111 inheritance field lets us mark the 'tax_id' uninheritable.
Do you still think it's necessary to rename the 'tax_id' field to something else for the company/system, or client, settings?
Tyson Phillips (Inactive)
added a comment - CORE-1111 inheritance field lets us mark the 'tax_id' uninheritable.
Do you still think it's necessary to rename the 'tax_id' field to something else for the company/system, or client, settings? Tyson Phillips (Inactive)
made changes -
| Status | Open [ 1 ] | Resolved [ 5 ] |
| Resolution | Fixed [ 1 ] |
No need to rename. Let's just make sure company tax_id setting is not inheritable.
Cody Phillips (Inactive)
added a comment - No need to rename. Let's just make sure company tax_id setting is not inheritable. I did a quick overview and found no invalid references, nor is it inherited when shown on the edit client page or invoices, even when the client setting doesn't exist.
Tyson Phillips (Inactive)
added a comment - I did a quick overview and found no invalid references, nor is it inherited when shown on the edit client page or invoices, even when the client setting doesn't exist. Tyson Phillips (Inactive)
made changes -
| Status | Resolved [ 5 ] | Closed [ 6 ] |
This looks like CORE-688 that could not be reproduced before.