Deploy Modified Metadata not deploying local-only files

Issue #206 resolved
Scott Wells repo owner created an issue

A user identified a potential issue with Deploy Modified Metadata where files that exist only in the local file system are not being deployed.

Comments (9)

  1. June Bischoff

    I'm not sure if this is related, but I've got my Validation & Deploy settings set up to validate (only) on edit and save. I have no luck deploying a new local-only file through Deploy Modified Metadata with these settings; I have to change my On Save setting to Deploy, and then it pushes to SF successfully.

    After the new file is pushed I can change my settings back to Validate on Edit/Save and can successfully push the file with Deploy Modified Metadata.

  2. Scott Wells reporter

    June, that's a limitation in Salesforce. You can't run a dry-run validation against something that doesn't yet exist in Salesforce. As a result, setting to validate-only will not yield results for files that haven't yet been deployed.

  3. June Bischoff

    I would expect Illuminated Cloud->Deploy Modified Metadata process to be able to push the local-only file to SF; that's the part that's failing when my settings are Validate only on Save. The only way to push the local file to SF is to change my settings to Deploy on Save and force save.

  4. Scott Wells reporter

    Let me rephrase that. You're saying that Deploy Modified Metadata should deploy and not validate. Yes, I agree. That's something I've been meaning to address for a while. I'll see if I can work that in very near-term.

  5. June Bischoff

    Nope! But I want them to deploy when I explicitly deploy them using Deploy Modified Metadata. It looks like it deploys and there's no error, but it's way too fast and the file doesn't show up in SF. I'm simply noting that the deploy success or failure appears to be dependent on the settings.

  6. June Bischoff

    Oh! I see what you're saying. Because it validates FIRST on Deploy Modified Metadata, it never gets around to actually deploying.

  7. Scott Wells reporter

    FYI, I'll have a fix for this in the next released build (either tomorrow morning or Monday morning).

  8. Log in to comment