Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

update messages for new GA data import commands #976

Merged
merged 1 commit into from
Jun 27, 2024
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions messages/tree.export.md
Original file line number Diff line number Diff line change
Expand Up @@ -46,8 +46,8 @@ Directory in which to generate the JSON files; default is current directory.

# PlanJsonWarning

After Nov 10, 2024, the JSON output for `--plan` will no longer include the `saveRefs` and `resolveRefs` properties.
Starting on Nov 10, 2024, the JSON output for `--plan` will no longer include the `saveRefs` and `resolveRefs` properties.

# LegacyDeprecation

After Nov 10, 2024, this command will no longer be available. Use `data export tree`.
Starting on Nov 10, 2024, this command will no longer be available. Use `data export tree` instead.
4 changes: 2 additions & 2 deletions messages/tree.import.md
Original file line number Diff line number Diff line change
Expand Up @@ -22,9 +22,9 @@ Plan definition file to insert multiple data files.

# flags.plan.description

Unlike the `--files` flag, the files listed in the plan definition file **can** contain more then 200 records. These will be automatically batched to comply with that limit.
Unlike when you use the `--files` flag, the files listed in the plan definition file **can** contain more then 200 records. When the CLI executes the import, it automatically batches the records to comply with the 200 record limit set by the API.

The file order matters--records with lookups to records in another file should be listed AFTER that file Example: you're loading Account and Contact records, and the contacts have references to those Accounts. The Accounts file should come before the Contacts file.
The order in which you list the files in the plan definition file matters. Specifically, records with lookups to records in another file should be listed AFTER that file. For example, let's say you're loading Account and Contact records, and the contacts have references to those accounts. Be sure you list the Accounts file before the Contacts file.

The plan definition file has the following schema:

Expand Down
1 change: 1 addition & 0 deletions src/commands/data/import/tree.ts
Original file line number Diff line number Diff line change
Expand Up @@ -37,6 +37,7 @@ export default class Import extends SfCommand<ImportResult[]> {
plan: Flags.file({
char: 'p',
summary: messages.getMessage('flags.plan.summary'),
description: messages.getMessage('flags.plan.description'),
exactlyOne: ['files', 'plan'],
exists: true,
}),
Expand Down
Loading