Uploaded image for project: 'Blesta Core'
  1. Blesta Core
  2. CORE-1076

Company tax_id inherited when no client tax_id set

    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

          Activity

          Hide
          tyson Tyson Phillips (Inactive) added a comment -

          This looks like CORE-688 that could not be reproduced before.

          Show
          tyson Tyson Phillips (Inactive) added a comment - This looks like CORE-688 that could not be reproduced before.
          Hide
          cody 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.

          Show
          cody 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.
          Hide
          tyson 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?

          Show
          tyson 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?
          Hide
          cody Cody Phillips (Inactive) added a comment -

          No need to rename. Let's just make sure company tax_id setting is not inheritable.

          Show
          cody Cody Phillips (Inactive) added a comment - No need to rename. Let's just make sure company tax_id setting is not inheritable.
          Hide
          tyson 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.

          Show
          tyson 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.

            People

            • Assignee:
              tyson Tyson Phillips (Inactive)
              Reporter:
              cody Cody Phillips (Inactive)
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:
                Fix Release Date:
                27/Aug/14