fortnox-api 1.0.0.rc11 → 1.0.0.rc12

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 7616a9760dec5aa02b7295ec094013aaffe962f98c402f613636a039f3d1891c
-  data.tar.gz: 6d8665d732a8f5125ad02991d2f9daf6277cef5cb9e9ce7123da32680f60a9f3
+  metadata.gz: 6a383d4f26222585f14be0a06145f63bb4584f8033e2eae2f91dc22cc513c085
+  data.tar.gz: 71fe26b84df2f8bb30ddcd990b39742606827b507164d42f8b05594b069f8ad6
 SHA512:
-  metadata.gz: 734e2f06e8e55583e789b9830092bcf6d53ee0d3b8511693cac15edab25a3658fd126d91ba18bcc8ebe33b823659a20494b16389c02adff0799b3faf8cf7a9bd
-  data.tar.gz: bf07508b1a70cbfabbba0fc9611866f2a87c3cb8fff564acfc9dbae3fca66d70fafbc2a1b8e1f5e594950800bb850fb5f592fdd38e4a61233d2f6568b8276411
+  metadata.gz: c22875f971a82ee3b75168da1395ef21c75bb04ef4e521d550264435c840b5ea786abcde67d8234eded0a06d9ad4028e1926403daf62a3ed8355ae9adfd9634f
+  data.tar.gz: '08b942421e226597317d74e1189b3a4aca90fcc5158d8b4f6d27d934a791f2af57f80c9226f406015372286187fd286e43d271fcdb8b2e501380001f55ce43f7'

data/CHANGELOG.md

@@ -8,6 +8,17 @@ and this project adheres to
 
 ## [Unreleased]
 
+## [1.0.0.rc12] - 2026-06-26
+
+### Fixed
+
+- `Fortnox::Customer` no longer sends `OrganisationNumber` when updating a
+  customer that has an active e-fakturakoppling
+  (`default_delivery_types.invoice == ELECTRONICINVOICE`). Fortnox rejects edits
+  to the org/personal number for such customers, and field-level dirty tracking
+  meant an unchanged `OrganisationNumber` was always included on update,
+  blocking every other update to those customers.
+
 ## [1.0.0.rc11] - 2026-06-26
 
 ### Changed
@@ -270,7 +281,8 @@ for the full list of breaking changes.
 For changes prior to the 1.0 rewrite, see the
 [0.x changelog](https://github.com/accodeing/fortnox-api/blob/v0.9.2/CHANGELOG.md).
 
-[Unreleased]: https://github.com/accodeing/fortnox-api/compare/v1.0.0.rc11...HEAD
+[Unreleased]: https://github.com/accodeing/fortnox-api/compare/v1.0.0.rc12...HEAD
+[1.0.0.rc12]: https://github.com/accodeing/fortnox-api/compare/v1.0.0.rc11...v1.0.0.rc12
 [1.0.0.rc11]: https://github.com/accodeing/fortnox-api/compare/v1.0.0.rc10...v1.0.0.rc11
 [1.0.0.rc10]: https://github.com/accodeing/fortnox-api/compare/v1.0.0.rc9...v1.0.0.rc10
 [1.0.0.rc9]: https://github.com/accodeing/fortnox-api/compare/v1.0.0.rc8...v1.0.0.rc9

data/lib/fortnox/resource.rb

@@ -24,23 +24,7 @@ module Fortnox
       end
     end
 
-    after_serialise do |data|
-      if meta.new?
-        # Strip nils for new records — rely on Fortnox defaults
-        data = data.compact
-      elsif __changes__.any?
-        # Send only the attributes passed to .update — field-level dirty
-        # tracking, not a value diff, so an attribute equal to its stored
-        # value is still sent, and an explicit nil reaches Fortnox as a clear.
-        changed_api_names = __changes__.keys.filter_map do |model_name|
-          self.class.all_attribute_definitions[model_name]&.api_name
-        end
-        data = data.slice(*changed_api_names)
-      end
-
-      # TODO: rest-easy should do this wrapping for us.
-      { config.instance_wrapper => data }
-    end
+    after_serialise { |data| default_after_serialise(data) }
 
     class << self
       attr_reader :registered_resources
@@ -135,5 +119,25 @@ module Fortnox
         }
       end
     end
+
+    private
+
+    # Shared serialisation tail used by the base after_serialise hook. Exposed
+    # as an instance method so subclass hooks can post-process the payload (e.g.
+    # drop a field) and still reuse it — rest-easy hooks override, not chain.
+    def default_after_serialise(data)
+      if meta.new?
+        # Strip nils for new records — rely on Fortnox defaults
+        data = data.compact
+      elsif __changes__.any?
+        # Send only the attributes passed to .update — field-level dirty
+        # tracking, not a value diff, so an attribute equal to its stored
+        # value is still sent, and an explicit nil reaches Fortnox as a clear.
+        data = data.slice(*__changes__.keys.filter_map { |name| self.class.all_attribute_definitions[name]&.api_name })
+      end
+
+      # TODO: rest-easy should do this wrapping for us.
+      { config.instance_wrapper => data }
+    end
   end
 end

data/lib/fortnox/resources/customer.rb

@@ -15,6 +15,15 @@ module Fortnox
       validate_electronic_invoice_delivery_type!(default_delivery_types&.invoice)
     end
 
+    # Fortnox refuses to edit OrganisationNumber once a customer has an active
+    # e-fakturakoppling. Drop it from the update payload in that case so the rest
+    # of the customer can still be updated. Field-level dirty tracking means an
+    # unchanged OrganisationNumber would otherwise always be sent on update.
+    after_serialise do |data|
+      data = data.except(organisation_number_api_name) if drop_organisation_number?
+      default_after_serialise(data)
+    end
+
     # Direct URL to the record.
     attr :url <=> '@url', Coercible::String.optional, :read_only
 
@@ -212,6 +221,14 @@ module Fortnox
 
     private
 
+    def drop_organisation_number? = !meta.new? && electronic_invoice_active?
+
+    def electronic_invoice_active?
+      default_delivery_types&.invoice == DefaultInvoiceDeliveryTypeValues['ELECTRONICINVOICE']
+    end
+
+    def organisation_number_api_name = self.class.all_attribute_definitions[:organisation_number].api_name
+
     # ELECTRONICINVOICE is only possible to set in the Fortnox UI.
     # Raise if a consumer tries to set it from this gem.
     def validate_electronic_invoice_delivery_type!(type)

data/lib/fortnox/version.rb

@@ -1,5 +1,5 @@
 # frozen_string_literal: true
 
 module Fortnox
-  VERSION = '1.0.0.rc11'
+  VERSION = '1.0.0.rc12'
 end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: fortnox-api
 version: !ruby/object:Gem::Version
-  version: 1.0.0.rc11
+  version: 1.0.0.rc12
 platform: ruby
 authors:
 - Jonas Schubert Erlandsson