New resources on IDE can't to deploy to Org.

[Sebastian Melgin]

Hi, I experimented an issue with the IDE (CE license). I created on IntelliJ a new resource and when I try to upload/deploy to my Salesforce Org (using menu -> Illuminated Cloud -> Force Save) the result is the IDE don't try to upload the resource (see on screenshot). With classes I have not problems to deploy when Save.

Using IntelliJ with Illuminated Cloud on Mac.

[Scott Wells]

Sebastian, is there anything in idea.log associated with this? You can see the log using Help>Show Log in Finder. If not, would you mind repeating this process with the following classes enabled for debug logging (Help>Debug Log Settings):

#com.illuminatedcloud.intellij.builder.ForceComBuilder
#com.illuminatedcloud.intellij.builder.ForceComMetadataApiDeployer

Then please supply the relevant portions of the log for the deployment. Thanks!

[Sebastian Melgin]

This is the idea.log file. I've trying to deploy "SetupPage3Js" to Org. The log says its ok but when I log onto my Dev Org, and go to Setup->Static Resources, it not found on it.

[Scott Wells]

Yeah, that's really strange. As you point out, I can see the static resource being added to the deployment archive, but the Salesforce deployment response doesn't include it as a success or a failure. How is your metadata subscription configured? Are you using All/Package? If so, would you mind switching to Selected and choosing just StaticResource, then trying the operation again? Let's see if that works and what the log shows.

[Sebastian Melgin]

Thanks for your help Scott. How/Where can I set the metadata subscription ?

[Scott Wells]

Go into File>Project Structure>Modules, expand your module, and click Illuminated Cloud*. You'll see three options for configuring your metadata subscription: All/Package, Package.xml, and Selected**. Let me know if that doesn't get you there.

[Sebastian Melgin]

The new log with "Force Save" option over SetupPage3Js.resource...

[Sebastian Melgin]

Done, Scott. Pls review the new log. Thanks !

[Scott Wells]

Thanks, Sebastian. Same result, unsurprisingly. I'll need to try to reproduce this on my end this evening or tomorrow. Do you mind trying one more thing, though? What happens if you just right-click on the static resource and click Illuminated Cloud>Deploy All Metadata? My guess is that the same thing will happen, but I'd like to know if this is something specific to the force save action or a more general issue with deployment.

I need to step away for a bit shortly, but I'll follow up with you either later tonight or, at the latest, tomorrow. Really sorry for the issue!

[Sebastian Melgin]

The new log.

[Sebastian Melgin]

Done, Scott. I attached the new log. No drama, S.. happens ! Tomorrow I'll be watching your comments. Thanks again for your cooperation.

[Scott Wells]

Sebastian, I've tried to reproduce this a few different ways -- creating a new static resource, force saving an existing static resource, deploying an existing static resource using "Deploy All Metadata" -- and all of them are working properly. Would it be possible for you to provide one of the static resources that's not deploying for you to me to see if there's something about the resource itself? Could you also try the same operation against a different org to see if it works properly there? It's just curious that Salesforce is giving a successful deployment response showing only package.xml.

[Sebastian Melgin]

Hi Scott, I'm outside the office untill 1pm (-05:00GMT) when arrive I send you the resource.

[Sebastian Melgin]

Hi Scott, I'm again at the office. I've attached the resource for you to test. Are you working on a IntelliJ with CE licensing ?

[Sebastian Melgin]

The resources I've tried to upload ...

[Scott Wells]

Thanks, Sebastian. I tried deploying it to one of my own orgs and it deployed no problem. Can you see if the same problem occurs if you try against another org?

I'm using IntelliJ IDEA Community Edition 2016.2, though I've tested this functionality all the way back to IDEA 12. I also just tried this on my Mac to see if that might be the difference, but the resource deployed no problem. Aside from the org, are you aware of any notable differences in this environment that might be contributing to the behavior?

[Sebastian Melgin]

Hi Scott. I don't know. Which variables can we consider for that ? OS El Capitan, I've attached system information.

[Sebastian Melgin]

System info.

[Scott Wells]

Yeah, that's really similar to my machine. Again, my suspicion is that it's something with the org. Can you try the same operation against another org, e.g., a free dev org, and see if you see the same behavior?

[Sebastian Melgin]

Hi Scott, the problem is extending to every class. I cannot update in the Org NOTHING. I cannot try in another org, it is time consuming and I need to finish some work for my company. Pls help to solve this in order to continue using your tool. I've attached the last log. Thx a lot.

[Sebastian Melgin]

Pls help to solve the problem... Thx.

[Scott Wells]

Sebastian, unfortunately where I'm unable to reproduce this, it's quite difficult to determine the root cause. What happens if you try the same deployment operations with other tools, e.g., the Force.com IDE? Does it succeed or behave similarly where it seems to succeed but doesn't actually do anything?

I'm about to jump on a flight and won't have much availability the rest of the afternoon. I'll check back in when I can.

[Scott Wells]

Sebastian, I'm reviewing backlog items and wondered if you were still hitting hit issue.

[Sebastian Melgin]

Hi Scott. I appreciate your concern, it talks about the company support. I really don't hit the issue any more.

Thanks a lot for your time.

[Scott Wells]

Glad to hear, Sebastian, and apologies for not having followed up with you much earlier.