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

Bug in API serialization of report details #13944

Closed
Haeki opened this issue Oct 2, 2023 · 0 comments · Fixed by #13958
Closed

Bug in API serialization of report details #13944

Haeki opened this issue Oct 2, 2023 · 0 comments · Fixed by #13958
Assignees
Labels
severity: low Does not significantly disrupt application functionality, or a workaround is available status: accepted This issue has been accepted for implementation type: bug A confirmed report of unexpected behavior in the application

Comments

@Haeki
Copy link

Haeki commented Oct 2, 2023

NetBox version

v3.6.3

Python version

3.11

Steps to Reproduce

  1. Access a report directly using the API for example /api/extras/reports/example_report.DeviceConnectionsReport/
  2. In the result some values are not serialized correctly.

Expected Behavior

The fields should be serialized correctly and results should be found.

Observed Behavior

The name and display fields have a property object that got not serialized.
image
Also the results could not be found

@Haeki Haeki added the type: bug A confirmed report of unexpected behavior in the application label Oct 2, 2023
@arthanson arthanson self-assigned this Oct 3, 2023
@arthanson arthanson added the severity: low Does not significantly disrupt application functionality, or a workaround is available label Oct 3, 2023
@jeremystretch jeremystretch added the status: accepted This issue has been accepted for implementation label Oct 3, 2023
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jan 2, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
severity: low Does not significantly disrupt application functionality, or a workaround is available status: accepted This issue has been accepted for implementation type: bug A confirmed report of unexpected behavior in the application
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants