mirror of
https://github.com/KelvinTegelaar/CIPP.git
synced 2026-04-25 08:16:01 +03:00
[GH-ISSUE #3476] Error: RAWJson is missing when editing Intune template name and description #1574
Labels
No labels
API
Feature
NotABug
NotABug
Planned
Sponsor Priority
Sponsor Priority
bug
documentation
duplicate
enhancement
needs more info
no-activity
no-priority
not-assigned
pull-request
react-conversion
react-conversion
roadmap
security
stale
unconfirmed-by-user
unconfirmed-by-user
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/CIPP#1574
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @mruiterHU on GitHub (Jan 27, 2025).
Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/3476
Description
Thanks for implementing my feature request faster than lightning: https://github.com/KelvinTegelaar/CIPP/issues/3453#issue-2809162503
Maybe I'm a bit early, and you guys are still working on it. But when I try to edit the template name and description, I get the error shown below. Someone else in the Discord tested it for me and got the same result.
It seems like the API isn’t retrieving the content of the policy, somewhere around line 22-27 in Modules/CIPPCore/Public/Entrypoints/HTTP Functions/CIPP/Core/Invoke-ExecEditTemplate.ps1?
Logbook Error:
Failed to edit template: Cannot bind argument to parameter 'RawJSON' because it is null.
Steps to reproduce:
Environment data
@github-actions[bot] commented on GitHub (Jan 27, 2025):
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://docs.cipp.app/
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!".
@mruiterHU commented on GitHub (Jan 27, 2025):
I confirm that I have checked the documentation thoroughly and believe this to be an actual bug.
@KelvinTegelaar commented on GitHub (Jan 27, 2025):
Fixed in dev