for Report & Dashboard meta files were excluded

amtrack / force-dev-tool

[DEPRECATED] Command line tool supporting the Force.com development lifecycle

MIT License

108 stars 37 forks source link

for Report & Dashboard meta files were excluded #102

Closed KevinGossentCap closed 6 years ago

KevinGossentCap commented 6 years ago

meta files exist to give access rights, they were excluded because of folder problem and meta set to false Changes solves folder problem but gives errors for report files not having meta (I don't see a way to deal with it for the moment)

amtrack commented 6 years ago

Hi @KevinGossentCap, you are right! This is indeed a problem.

Regarding your proposed change:

I would prefer a solution without changing the lib/describe-metadata-result.json file as this is what we get from the API on calling describeMetadata().
Further i think that force-dev-tool should differentiate Report and ReportFolder.

Can you please test #103 and tell me if that's what you need?

Last but not least can you please provide some more information for me to fully understand this. What were you trying to do and what are you expecting as outcome?

KevinGossentCap commented 6 years ago

Hi @amtrack , I've just tested it on my diff and it does the job 👍 On my side I'm trying to dig the possibilities of force-dev-tool to be able to build the right delta and thus reduce the components pushed each time instead of nearly pushing everything. Here it was the sharing parameters of the folders that were absent which now is solved.

I'll start looking at another one concerning profiles (seems some diffs are seen but files are not in the output folder even if they are present in the package.xml output file). I'll dig a little and try to find a minimal diff to help people dig if I'm stuck.

amtrack commented 6 years ago

Implemented in #103