Skip to content
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

Restriction Rules not supported in Source format #1158

Closed
jhawk-4 opened this issue Aug 27, 2021 · 3 comments
Closed

Restriction Rules not supported in Source format #1158

jhawk-4 opened this issue Aug 27, 2021 · 3 comments
Labels
bug Issue or pull request that identifies or fixes a bug investigating We're actively investigating this issue

Comments

@jhawk-4
Copy link

jhawk-4 commented Aug 27, 2021

Summary

We are trialing Restriction Rules (beta in v52.0). The metadata coverage report indicates that this metadata is supported both the Metadata API and Source Tracking. When attempting to convert from source format to mdapi format, the metadata is treated as a ModerationRule instead of RestrictionRule.

Steps To Reproduce:

Repository to reproduce: Sample Repo

  1. Clone the sample repo
  2. run sfdx force:source:convert -d ./mdapi

Expected result

Source is converted to metadata API format with a restrictionRules folder and the package.xml should reference the RestrictionRule metadata type.

Actual result

Source is converted to metadata API format with a moderation folder instead of restrictionRules. The package.xml file also defines the metadata type as ModerationRule instead of RestrictionRule.

System Information

{
        "cliVersion": "sfdx-cli/7.114.0",
        "architecture": "darwin-x64",
        "nodeVersion": "node-v14.17.5",
        "pluginVersions": [
                "@oclif/plugin-autocomplete 0.3.0 (core)",
                "@oclif/plugin-commands 1.3.0 (core)",
                "@oclif/plugin-help 3.2.2 (core)",
                "@oclif/plugin-not-found 1.2.4 (core)",
                "@oclif/plugin-plugins 1.10.1 (core)",
                "@oclif/plugin-update 1.4.0-3 (core)",
                "@oclif/plugin-warn-if-update-available 1.7.0 (core)",
                "@oclif/plugin-which 1.0.3 (core)",
                "@salesforce/sfdx-diff 0.0.6",
                "@salesforce/sfdx-plugin-lwc-test 0.1.7 (core)",
                "@salesforce/sfdx-trust 3.6.0 (core)",
                "alias 1.1.10 (core)",
                "apex 0.2.7 (core)",
                "auth 1.7.1 (core)",
                "config 1.2.23 (core)",
                "custom-metadata 1.0.12 (core)",
                "data 0.6.0 (core)",
                "generator 1.1.7 (core)",
                "limits 1.2.1 (core)",
                "org 1.6.9 (core)",
                "salesforce-alm 52.2.5 (core)",
                "schema 1.0.8 (core)",
                "sfdx-cli 7.114.0 (core)",
                "source 1.0.9 (core)",
                "telemetry 1.2.3 (core)",
                "templates 52.1.0 (core)",
                "user 1.4.0 (core)"
        ],
        "osVersion": "Darwin 20.5.0"
}
@jhawk-4 jhawk-4 added the investigating We're actively investigating this issue label Aug 27, 2021
@github-actions
Copy link

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.

@mshanemc mshanemc added the bug Issue or pull request that identifies or fixes a bug label Aug 30, 2021
@uip-robot-zz
Copy link

This issue has been linked to a new work item: W-9833678

@shetzel
Copy link
Contributor

shetzel commented Sep 1, 2021

Super easy fix. Should be in the next CLI release candidate.

Edit: Also, thanks for the repo and all the details. That definitely contributed to the speed of the fix. 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Issue or pull request that identifies or fixes a bug investigating We're actively investigating this issue
Projects
None yet
Development

No branches or pull requests

5 participants