Closed Nickers3 closed 4 years ago
@mkolodner I created a pull request so you can comment on the work you are doing.
From the looks for the pull request, the datasets/sample.sql is different so we will need to update
What is the error you are getting on the qa org?
Got it. Didn't realize making the pull request was the next step. (And didn't really want to make one until I was sure it worked.) Yes, it's the dataset that has changed, and the mapping.yml. I'm pretty confident they're right. But I can't spin up a QA org to test because of that error. I'm trying one more time so I can also copy the error. (I accidentally quit VS Code, so lost the error message.)
@mkolodner typically I wait to merge into master until I have tested the dev_org flow and have been successful. The pull request is the way to track commits and compare against master.
And I apparently blew it when I did the conflict resolve. I'm working on recovering from my mistake. Watch this space.
I think there is a way to revert to a previous commit. For the data ones, it may be best to revert to prior to the commit I did yesterday, then try to resolve via the branch you are in.
And my QA org just failed: 2020-06-12 13:13:49: Running step: Insert Contact 2020-06-12 13:13:49: Extracting Record Types for Contact 2020-06-12 13:13:51: Prepared 24 rows for insert to Contact 2020-06-12 13:13:51: Uploading batch 1 2020-06-12 13:13:53: Waiting for job 75054000006RmRJAA0 (1/1 batches complete) 2020-06-12 13:13:53: Job 75054000006RmRJAA0 finished with result: Row failure 2020-06-12 13:13:54: Downloaded results for batch 75154000006OUk1AAG 2020-06-12 13:13:54: Exception in task config_qa.load_dataset
Error: Error on record with id 0030R000012LqMuQAK: INVALID_CROSS_REFERENCE_KEY:Record Type ID: this ID value isn't valid for the user: 01254000001maS1AAI:RecordTypeId -- Run this command for more information about debugging errors: cci error --help Michaels-MacBook-Pro:OmbudsmanCloudCare michaelkolodner$
Also of note @Nickers3 : I pulled up that QA org and the Case Reason options aren't there at all, not even as inactive.
Can you do an export from the scratch org to see which recordtype ID that is. My gut says it's because the contact record types are not enabled for the org. With the work I'm doing, that would get resolved.
Nickers nick@stlf.net
On Fri, Jun 12, 2020 at 12:16 PM Michael Kolodner notifications@github.com wrote:
And my QA org just failed: 2020-06-12 13:13:49: Running step: Insert Contact 2020-06-12 13:13:49: Extracting Record Types for Contact 2020-06-12 13:13:51: Prepared 24 rows for insert to Contact 2020-06-12 13:13:51: Uploading batch 1 2020-06-12 13:13:53: Waiting for job 75054000006RmRJAA0 (1/1 batches complete) 2020-06-12 13:13:53: Job 75054000006RmRJAA0 finished with result: Row failure 2020-06-12 13:13:54: Downloaded results for batch 75154000006OUk1AAG 2020-06-12 13:13:54: Exception in task config_qa.load_dataset
Error: Error on record with id 0030R000012LqMuQAK: INVALID_CROSS_REFERENCE_KEY:Record Type ID: this ID value isn't valid for the user: 01254000001maS1AAI:RecordTypeId -- Run this command for more information about debugging errors: cci error --help Michaels-MacBook-Pro:OmbudsmanCloudCare michaelkolodner$
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/SFDO-Community-Sprints/OmbudsmanCloudCare/pull/32#issuecomment-643391668, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACUVOYRC5IRV5XUORXEKVGDRWJPIHANCNFSM4N4O4YWA .
I kinda' can't. I don't really know what you mean and I'm so frustrated right now I don't even want to try.
Hang in there!! CCI is a tool of power. It's a learning curve to figure it out so you'll get there.
I pulled my work to your repo on my computer and got a new error:
Exception in task config_dev.load_dataset
Error: table Account has 16 columns but 15 values were supplied
Think it's something to do with the blanks. Running a import now to see if this fixes it.
Got it working on an import. Trying again to see if I can get it working on new.
Critical Changes
Changes
Issues Closed