[GH-ISSUE #1378] Dynamic Group template adds extra \'s #760

Closed
opened 2026-03-02 12:44:59 +03:00 by kerem · 2 comments
Owner

Originally created by @RedRhombus001 on GitHub (Feb 13, 2023).
Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/1378

Description

I have created a dynamic group template. This group existed in another tenant. To make the template I copied the data from what CIPP displayed when I looked at the group properties.

Example of the dynamic group properties that I copied.
(device.devicePhysicalIDs -any (_ -eq "[OrderID]:Autopilot-SelfDeploying")) -and ((device.devicePhysicalIDs -any (_ -contains "[ZTDId]")) -or (device.deviceOwnership -eq "Company"))

Example of the properties of the group template.
(device.devicePhysicalIDs -any (_ -eq \"[OrderID]:Autopilot-SelfDeploying\")) -and ((device.devicePhysicalIDs -any (_ -contains \"[ZTDId]\")) -or (device.deviceOwnership -eq \"Company\"))"

This then returns an error when deploying of: Failed to create group. Invalid characters found in the rule: \ \ \

If I then deploy the group it shows the correct dynamic group string without the extra \. But still returns an error.
If I change the dynamic group string (copy and paste) before pressing submit, it also returns the same error.

Environment data

Azure 
Frontend: 3.0.0 
Backend: 3.0.0
Originally created by @RedRhombus001 on GitHub (Feb 13, 2023). Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/1378 ### Description I have created a dynamic group template. This group existed in another tenant. To make the template I copied the data from what CIPP displayed when I looked at the group properties. Example of the dynamic group properties that I copied. (device.devicePhysicalIDs -any (_ -eq \"[OrderID]:Autopilot-SelfDeploying\")) -and ((device.devicePhysicalIDs -any (_ -contains \"[ZTDId]\")) -or (device.deviceOwnership -eq \"Company\")) Example of the properties of the group template. (device.devicePhysicalIDs -any (_ -eq \\\"[OrderID]:Autopilot-SelfDeploying\\\")) -and ((device.devicePhysicalIDs -any (_ -contains \\\"[ZTDId]\\\")) -or (device.deviceOwnership -eq \\\"Company\\\"))" This then returns an error when deploying of: Failed to create group. Invalid characters found in the rule: \ \ \ If I then deploy the group it shows the correct dynamic group string without the extra \\\. But still returns an error. If I change the dynamic group string (copy and paste) before pressing submit, it also returns the same error. ### Environment data ```PowerShell Azure Frontend: 3.0.0 Backend: 3.0.0 ```
kerem 2026-03-02 12:44:59 +03:00
Author
Owner

@github-actions[bot] commented on GitHub (Feb 13, 2023):

Thank you for creating a bug. Please make sure your bug is indeed a unique case by checking current and past issues, and reading the complete documentation at https://kelvintegelaar.github.io/CIPP
If your bug is a known documentation issue, it will be closed without notice by a contributor. To confirm that this is not a bug found in the documentation, please copy and paste the following comment: "I confirm that I have checked the documentation thoroughly and believe this to be an actual bug.".

Without confirming, your report will be closed in 24 hours. If you'd like this bug to be assigned to you, please comment "I would like to work on this please!".

<!-- gh-comment-id:1428820680 --> @github-actions[bot] commented on GitHub (Feb 13, 2023): Thank you for creating a bug. Please make sure your bug is indeed a unique case by checking current and past issues, and reading the complete documentation at https://kelvintegelaar.github.io/CIPP If your bug is a known documentation issue, it will be closed without notice by a contributor. To confirm that this is not a bug found in the documentation, please copy and paste the following comment: "I confirm that I have checked the documentation thoroughly and believe this to be an actual bug.". Without confirming, your report will be closed in 24 hours. If you'd like this bug to be assigned to you, please comment "I would like to work on this please!".
Author
Owner

@KelvinTegelaar commented on GitHub (Feb 15, 2023):

Fixed in dev

<!-- gh-comment-id:1431649156 --> @KelvinTegelaar commented on GitHub (Feb 15, 2023): Fixed in dev
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/CIPP#760
No description provided.