multi identifier preference record uploads

[JonnavithulaGirish]

Related Issues

• closes PIK-166

Usage

pnpm start consent upload-preferences --auth=your-auth-token --partition=your-partition --directory=./examples/pm-test --dryRun=true --skipWorkflowTriggers=true --skipExistingRecordCheck=true --isSilent=true --attributes="Tags:transcend-cli,Source:transcend-cli" --transcendUrl=https://api.transcend.io/ --allowedIdentifierNames="email,personId,memberId" --identifierColumns="email_id,person_id,member_id"

---

Note

Introduces a new CLI command to upload preference records from CSV with multi-identifier support, including interactive/batch flows, parsing, GraphQL integration, receipts, and examples.

• CLI: consent upload-preferences
  • Core: command.ts, impl.ts, buildTaskOptions.ts, worker.ts
  • Upload flows: upload/batchUploader.ts, upload/buildInteractiveUploadPlan.ts, upload/interactivePreferenceUploaderFromPlan.ts, upload/types.ts
  • Transform: upload/transform/transformCsv.ts, buildPendingUpdates.ts, index.ts
  • Artifacts/receipts: artifacts/receipts/index.ts, receiptsState.ts
  • Docs: readme.ts
• Preference Management Library:
  • Parsing: parsePreferenceManagementCsv.ts, parsePreferenceFileFormatFromCsv.ts, parsePreferenceIdentifiersFromCsv.ts, parsePreferenceAndPurposeValuesFromCsv.ts
  • Logic: getPreferencesForIdentifiers.ts, getPreferenceUpdatesFromRow.ts, codecs.ts, uploadPreferenceManagementPreferencesInteractive.ts, index.ts
• GraphQL: createSombraGotInstance.ts, makeGraphQLRequest.ts, gqls/RequestDataSilo.ts
• Helpers: collectCsvFilesOrExit.ts, pooling/logRotation.ts
• Examples: CSV samples under examples/pm-test/
• Schema/Docs: transcend-yml-schema-v9.json, updates to README.md and CHANGELOG.md

^{Written by Cursor Bugbot for commit f8a91f9. This will update automatically on new commits. Configure here.}

[linear]

PIK-166 Fix prferences CLI to handle mutliple identifiers

[bencmbrook]

The preferred pattern for lists is to use the built-in variadic: ','. This will parse it in the same way, but it will also (A) provide better error messages for malformed inputs, and (B) it will also self-document that it's a list which can be provided as a comma-separated argument like this:

FLAGS
      --auth                    The Transcend API key.
     [--identifierColumns]...   Identifier names configured for the run. [separator = ,]

It also allows users to pass --identifierColumns 1 --identifierColumns 2 --identifierColumns 3

And if any of these are enums (I don't think they are, but) you can also do something like this to validate (and also self-document) the expected inputs:

If you

Suggested change

	allowedIdentifierNames: {
	kind: 'parsed',
	parse: (value: string) => value.split(',').map((s) => s.trim()),
	brief:
	'Identifiers configured for the run. Comma-separated list of identifier names.',
	},
	identifierColumns: {
	kind: 'parsed',
	parse: (value: string) => value.split(',').map((s) => s.trim()),
	brief:
	'Columns in the CSV that should be used as identifiers. Comma-separated list of column names.',
	},
	columnsToIgnore: {
	kind: 'parsed',
	parse: (value: string) => value.split(',').map((s) => s.trim()),
	brief:
	'Columns in the CSV that should be ignored. Comma-separated list of column names.',
	optional: true,
	allowedIdentifierNames: {
	kind: 'parsed',
	parse: String,
	variadic: ',',
	brief: 'Identifier names configured for the run.',
	},
	identifierColumns: {
	kind: 'parsed',
	parse: String,
	variadic: ',',
	brief: 'Columns in the CSV that should be used as identifiers.',
	},
	columnsToIgnore: {
	kind: 'parsed',
	parse: String,
	variadic: ',',
	brief: 'Columns in the CSV that should be ignored.',
	optional: true,

[michaelfarrell76]

restore

[cursor]

Bug: Incorrect Parameter Order in setValue Calls

The setValue calls in parsePreferenceFileFormatFromCsv.ts and parsePreferenceAndPurposeValuesFromCsv.ts pass parameters in the wrong order, using (value, key) instead of the expected (key, value). This is inconsistent with getValue's key-first convention and likely results in incorrect state updates.

Additional Locations (1)

• src/lib/preference-management/parsePreferenceAndPurposeValuesFromCsv.ts#L209-L210

 

[cursor]

Bug: Fix: incorrect default uploadConcurrency value persisted

The comment "// FIXME 25" on line 114 suggests the default value for uploadConcurrency should be 25 instead of 75, but was left at 75. This appears to be temporary debugging code or an unfinished change that was accidentally committed.