-
-
Notifications
You must be signed in to change notification settings - Fork 863
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
Custom Attributes Assigned to Quotes Are Not Visible #1789
Comments
Hello, what about the resolution of this bug? |
Hi @dev-serge-assur, the PR raised for this issue will be included in the next patch release, and the issue will be fixed. PR link-#1871 |
Hello @shivendra-webkul, thanks for your feedback, I can now see the custom attribute but a small problem, when the attribute is of file type, when saving there is no trace of this file in the database. Maybe also the same with the other types. You can check on your side too |
@dev-serge-assur, thank you for bringing this to our attention. We will investigate the issue and provide you with an update shortly. |
Checked and Found that the custom attribute which as been assigned to the quote are now visible in Quote Form. Please check the video for reference. Video Quote.mp4 |
Hello @ashishkumar-webkul, check this comment #1789 (comment) |
Fixed issue #1789 (Custom Attributes Assigned to Quotes Are Not Visible)
Bug Report
Title
Custom Attributes Assigned to Quotes Are Not Visible
Issue Description
After creating a custom attribute and assigning it to Quotes, the assigned fields (e.g., Text, Text Area, Boolean, etc.) do not appear as expected. This issue prevents users from utilizing the custom attributes within the Quotes module.
Steps to Reproduce
Expected Result
The assigned custom attribute fields (e.g., Text, Text Area, Boolean) should appear within the Quotes module and function as configured.
Actual Result
The custom attribute fields are not visible in the Quotes module, making them inaccessible.
Acceptance Criteria
Attachments:
No.vakue.mp4
The text was updated successfully, but these errors were encountered: