Hi Brent,

We have (not always obvious) separation of deploying changes to the organization - everything that's related to the code (+ static resources) is deployed using the "Build" command, however, for everything else you need to use "Deploy Objects" command. It is available in the context menu of the project in the Solution Explorer and from the "Build" menu. (a bit more info in our documentation)

For all the metadata types that are deployed using the "Deploy Objects" there's no tracking (yet) in the Pending Changes panel as well as "Output" panel is not updated by this process - we have this improvements in our backlog for a while and at some point later we will implement them or we'll change the "update" process to be the same for all metadata types.

Hope this answers.

Thank you,

Vladimir

I see.  Thank you, Vladimir.  Is the only current options to deploy *all* non-code component types then?  And will it only send those files that have changed locally?

Hi Brent,

Yup, for now "Deploy objects" will look for changes in all types and will deploy only changed ones.

The only difference in this approach is now available for FLS, sObjects, Layouts and Permission Sets - from their corresponding editors (sObjects inspector with different tabs, or Permission Sets editor) you have an option to deploy only one item that is opened in the editor.

Taking into account our plans to work on the Workflows and Validations soon - such options will be available for them, but a bit later.

Thank you,

Vladimir