Hi Sebastien,

Thank you for the tool for generating package,
We would like to add few more metadata on for project.

"navigationMenus": {
"xmlName": "NavigationMenu",
"minApiVersion": 27.0,
"maxApiVersion": 52.0
},
"audience": {
"xmlName": "Audience",
"minApiVersion": 27.0,
"maxApiVersion": 52.0
},

Kindly consider.

Hi,

Translations files are ignored and cannot be found in the package.xml after running the script.
examples:
src\translations\en_US.transltion
src\standardValueSetTranslaions\CaseStatus-en_US.standardValueSetTranslation

API Version: 43.0

Thanks!

Hi Sebastien.

I've found the issue: your package create an WorkflowAlert node in the package.xml file instead of a CompactLayout node:

Need to add these elements in metada.js

metadata.zip

Hi,
I encounter the following issue:
One of the build failed on:

(node:13526) UnhandledPromiseRejectionWarning: Unhandled Promise Rejection (rejection id: 2): Error Unexpected close tag Line 35581 Column 15 Char: >

(node:13256): [DEP0018] DeprecationWarning: Unhandled Promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

The solution was running the sgp command on each folder (that contain the objects) ,until we found the directory that contain the failed object .Then inside the directory run the sgp until we found the object that cause the failure
Is it possible that the sgp command will print the file that cause the failure ?
regards

Hi Sebastien.
I've noticed that your package doesn't handle a Metadata Type TopicsForObjects.
Could you please resolve this small issue?
Thanks.

Hi, I was using jsforce to deploy metadata base on api ver 37.0 and it occurred Unknown type error as title.

Hi Sebastien.

I've faced issue:

(node:77781) UnhandledPromiseRejectionWarning: Error: Non-whitespace before first tag.
Line: 0
Column: 1
Char: 
    at error (/usr/local/lib/node_modules/sfdc-generate-package/node_modules/sax/lib/sax.js:651:10)
    at strictFail (/usr/local/lib/node_modules/sfdc-generate-package/node_modules/sax/lib/sax.js:677:7)
    at beginWhiteSpace (/usr/local/lib/node_modules/sfdc-generate-package/node_modules/sax/lib/sax.js:951:7)
    at SAXParser.write (/usr/local/lib/node_modules/sfdc-generate-package/node_modules/sax/lib/sax.js:1006:11)
    at Parser.exports.Parser.Parser.parseString (/usr/local/lib/node_modules/sfdc-generate-package/node_modules/xml2js/lib/parser.js:322:31)
    at Parser.parseString (/usr/local/lib/node_modules/sfdc-generate-package/node_modules/xml2js/lib/parser.js:5:59)
    at Promise (/usr/local/lib/node_modules/sfdc-generate-package/lib/utils/async-xml-parser.js:6:12)
    at new Promise (<anonymous>)
    at parseStringAsync (/usr/local/lib/node_modules/sfdc-generate-package/lib/utils/async-xml-parser.js:4:19)
(node:77781) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 2)
(node:77781) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

Looks like an issue in libraries that you've used.
But maybe you know how to resolve it quickly.

Thanks! :)

Due to generating manifest, if some metadata exist in api and don't exist in soap api it not appear in metadata.js file. Hope you still care about this tool ;)

Lacking metadata - permissionsetgroups

After adding it it to file, works like charm, please add this metadata.

  "permissionsetgroups": {
    "xmlName": "PermissionSetGroup",
    "minApiVersion": 45.0,
    "maxApiVersion": 47.0
  },

P.S. and update to API 48

Hi,

I would like to consult with you about a change i want to make.
The idea is to run the metadata API each time to retrieve the version specific metadata so it will be future proof without having to update metadata.js manually in the repository each version release.

The user will have to input in the cli a username and password of an org (any org, since the metadata api result will be the same for every org) and build the metadata.js in memory instead of using metadata.js repository file.

The problem is that i guess not every company will be willing to make a callout from this package, or to input their org credentials.

So there are few options:

1. Force everybody to work with metadata API to use this package (my favorite)
2. Build some NodeJS app that will run on heroku/Google Cloud Functuin with a Trailhead Playground org credentials and the package will send a request to that endpoint and receive the metadata of a specific version, this way companies won't have to use their org credentials, but they will be allowed to choose if to use our endpoint or the real metadata api.
3. use option 1 or 2 and still maintaining the metadata.js manually for companies that will still want to work offline with this package

Please tell me what is your preferred work of action and i'll try to implement.
If you would like to discuss further about it, you can get my email from Ben Bozou.

Best regards,

Ariel

Hello,

I use this module in a gulp task, calling it before the deploy task from "gulp-jsforce-deploy" module.
When deploying my package based on the generated package.xml, The deployment status on the instance fails because the module added a node with the name of the folder where my Email Templates are located.

Hereafter the gulp taks:

gulp.task('build-package', () => {
    sgp({
        apiVersion: forceConfig.apiVersion,
        src: forceConfig.src,
        output: forceConfig.src
    });
});

gulp.task('deploy', ['build-package'], () => {
    gulp.src('./' + forceConfig.src + '/**', { base: '.' })
      .pipe(zip('package.zip'))
      .pipe(forceDeploy({
          username: forceConfig.username,
          password: forceConfig.password,
          loginUrl: forceConfig.url,
          version: forceConfig.apiVersion,
          pollInterval: forceConfig.pollInterval,
          pollTimeout: forceConfig.pollTimeout
      }));
});

My folder structure is like this:
| emails
--| unfiled$public
----| myTemplate1
----| myTemplate2

Here is the generated package.xml file (EmailTemplate part):

<types>
    <members>unfiled$public</members>
    <members>unfiled$public/myTemplate1</members>
    <members>unfiled$public/myTemplate2</members>
    <name>EmailTemplate</name>
 </types>

The issue in the deployment status is An object 'unfiled$public' of type EmailTemplate was named in package.xml, but was not found in zipped directory.

I think you should juste escape the potential folder structure between the emails folder and the templates files.

Let me know if you need further details.

sgp -s ./src -a 43.0 -o ./src

(node:11436) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 1): TypeError: Cannot read property 'objects' of undefined

(node:11436) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

Need to add these elements in metada.js

Need to add these elements in metada.js

Hi,

When generating a package.xml from folders containing queueRoutingConfigs, it seems that they are ignored. Could you please add them?

Thanks

In the "subdefinition-type-strategy" file, on the line 26, there are "this.metadata" but the class aren't this attribute.
Prefer use "metadata" directly

Error:

TypeError: Cannot read property 'objects' of undefined
at result.forEach.aFile (C:\Users\baptiste.bieber\Documents\Dev\sfdc-extended-metadata\node_modules\sfdc-generate-package\lib\strategies\type-strategies\subdefinition-type-strategy.js:26:27)

Hi,

When generating a package.xml from folders containing custom permissions, it seems that they are ignored. Could you please add them?

Thanks

Currently the package.xml script that is generated will include folders within a metadata type as members of that metadata type making the package.xml look for a file that does not exist.

We need to not include the folders as members e.g.

<types>
    <members>Folder</members>
    <members>Folder/Email_Template</members>
    <name>EmailTemplate</name>
</types>

The Folder member does not exist but is included in the package.xml. This should not be included as it is inferred from the path of the Email Template.

Hi

Thanks for this tool to generate package.xml from source code.

But it could not able to add memebers for workflow.

Also, it can't able to add wave components.

Could you please look into this?

Thanks,
Venkat

Hi guys when adding Lightning Web Components to the source (LWC folder), the "LightningComponentBundle" type is not generated on the package.xml file.

Thanks in advance

Email templates are not been taken into account when generating the package.xml