-
Notifications
You must be signed in to change notification settings - Fork 78
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Deployment error table is missing Metadata type. Inconsistent naming of table headers. #3110
Comments
Thank you for filing this issue. We appreciate your feedback and will review the issue as soon as possible. Remember, however, that GitHub isn't a mechanism for receiving support under any agreement or SLA. If you require immediate assistance, contact Salesforce Customer Support. |
This issue has been linked to a new work item: W-17227008 |
@PawelWozniak - I put up a PR to repurpose the |
@WillieRuemmele Thank you for your work, that will help all developers. |
This has been released into |
Summary
When I get error in SF CLI for metadata verification then it is inconsistent with what I can see in SF gui.
In example above seeing only error in CLI I am confused what it is about as object was already deleted.
When I check for the error in deployment verification status in GUI I see additional "Type" column with value "Tab" now I understand that there is something wrong with tab metadata related to deleted object.
Please add "Metadata Type" column in CLI so it is clear what error is about.
Also Line and Column value is missing in this example. I know that it might be not relevant in case of the tab metadata but still it is inconsistent with GUI.
Steps To Reproduce
Unable to provide exact steps. In my case I had and object and custom tab. Then object was deleted.
Expected result
As developer which is using mainly VSCode and CLI I see clear error message in CLI so I know what it is about.
Actual result
I am missing information about which metadata type error is shown and where (line and column).
System Information
The text was updated successfully, but these errors were encountered: