SFDX Pull action isn't pulling all the profiles properly

Issue #782 resolved
Javier García Manzano created an issue

Upon the following action, the tool doesn't behave as expected:

  1. Create some metadata
  2. Give permissions to every profile
  3. Pull to Local enviroment

And then the profiles aren't pulled properly. Only 3 out of 6 profiles are pulled as expected. The remaining 3 are untouched.

Why is this happening?


Comments (5)

  1. Scott Wells repo owner

    Javier, unfortunately IC doesn't have any control over what SFDX decides to push and pull. IC is just a driver for the CLI via it's programmatic calling interface. Can you verify that the same behavior occurs when you run sfdx force:source:pull from the command-line just to verify that 100%, though? If that's the case, you'll likely need to ask this question on the Salesforce DX Success Community feed where I'm sure you'll get a very quick response from the SFDX team.

  2. Javier García Manzano reporter

    Yeah, I checked it out. Sadly, DX isn't as mature as we'd like it to be, but thanks again for all the hassle!

  3. Luke Kozakewycz

    I'm trying to retrieve a permission set, but I can't seem to find a way to do so via SFDX. I have only 5 days to do so! Uh-oh.

  4. Scott Wells repo owner

    So a couple of things. First, here's a potential workaround...create another user in the scratch org and connect IC to it as a standard connection, then use IC to pull down the metadata you need. It'll come down in metadata form so you'll need to rename it to source form, basically ProfileName.profile will be renamed to ProfileName.profile-meta.xml or same with .permissionset. That will help you get it out of the org and into your local filesystem. Second, have you guys reported this on the SFDX Success Community? If not, I would recommend you do so as that's the primary feedback channel to the team.

  5. Scott Wells repo owner

    Sounds like this is an SFDX issue so I'm resolving it, but happy to continue offering thoughts on how to use IC to work around these challenges if required. Also, if it turns out it is an IC issue, just reopen with the details.

  6. Log in to comment