Skip to content

[BUG] Custom metadata columns are always formatted using toString() in the message browser. #75

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.

Sign up for GitHub

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

Jump to bottom
Open
rogin opened this issue Apr 30, 2025 · 1 comment
Open

[BUG] Custom metadata columns are always formatted using toString() in the message browser. #75

rogin opened this issue Apr 30, 2025 · 1 comment
Labels
bug Something isn't working

Comments

@rogin
Copy link
Contributor

rogin commented Apr 30, 2025 •
edited by jonbartels
Loading

Describe the bug
I'm migrating popular requests from NextGen's repo. This was issue #6203

When using a non-STRING type for a custom Metadata, the dashboard should use a readable format instead of using the default "toString()", which sometime results in unreadable information.

Additional context
I or another can copy over the details is-simon provided. It may be undeleting a few lines to get this working again.
@rogin rogin added the bug Something isn't working label Apr 30, 2025
@sbraconnier
Copy link

I'll take care of this one...

sbraconnier added a commit to sbraconnier/oie-engine that referenced this issue May 17, 2025
@sbraconnier
Use proper renderer for custom metadata columns (OpenIntegrationEngin…
d053504 
…e#75)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@rogin @sbraconnier