Problem
After upgrading to a newer Kaptio version, users encounter errors when attempting to add component options to packages. The error occurs because a new required picklist field ‘Booking Wizard Unit Number Selection’ (KaptioTravel__PhysicalInventorySelection__c) was introduced on the Package object, but existing Package records do not have this field populated.
What We Found
The new field KaptioTravel__PhysicalInventorySelection__c on the Package object is a Required picklist. When any update is attempted on existing Package records (including via custom triggers, component option additions, or direct edits), Salesforce validation fails because the required field is empty. This affects any customer with existing Package data who upgrades to versions containing this field.
Solution
- Run a data update to populate KaptioTravel__PhysicalInventorySelection__c on ALL existing Package records with the value ‘NotMandatoryHidden’
- Navigate to Setup → Object Manager → KaptioTravel__Package__c → Fields & Relationships → KaptioTravel__PhysicalInventorySelection__c
- Edit the picklist values and set ‘NotMandatoryHidden’ as the default value for new records
- Ensure all relevant Permission Sets include read access to the KaptioTravel__PhysicalInventorySelection__c field (add to permission sets like ‘(Kaptio) Build Trips & Itineraries’)
- Test by adding a component option to an existing package to verify the error is resolved
Notes
- The field controls whether cabin/unit selection is mandatory in the Booking Wizard - ‘NotMandatoryHidden’ means the Select Cabin tab will be hidden, allowing itineraries to be created without selecting a cabin
- When the tab is disabled, the Pricing Summary displays a Cabin Description label with the associated Cabin Type shown beneath it
- This should be included in upgrade handover documentation for all customer upgrades
- Users may also need FLS access to related new fields: KaptioTravel__IsPredefinedManualRail__c, KaptioTravel__TourDeparture__c (on Itinerary Item), KaptioTravel__AllowChangePackageDepartureDate__c (on Package Departure), KaptioTravel__CumulativePricing__c (on Price Category)
Warnings
⚠️ Any custom triggers that update Package records will also fail if this field is not populated ⚠️ This is a data migration issue - simply granting field permissions is not sufficient; the field values must be populated on existing records
Source: KHELP-12296