Hi all, we are using SCA Elbrus in our website. We want to show a custom Sales Order field on the frontend, we've added it to the SC Configuration and we have checked the Web Store field on the field. We are still getting a Permissions Violation after requesting the live order. We are wondering if the change on the field for the Web Store takes a bit of time to reflect or if we are missing any steps

What type of custom transaction field is it? Is it a list/record field that’s pointing to a record type that the customer center or shopping roles do not have permission to access?

Its a custbody checkbox field. For some reason we are getting the value on the frontend, but on the logs we’ve this error: Permission Violation: You need the ‘Transactions -> Sales Order’ permission to access this page. Please contact your account administrator. Its the Customer Center role, and it has the permission to Edit Sales Orders. Also we tried using another higher role. This error only happens when the custbody its exposed with the Configuration List

Where did you define the field in SuiteCommerce Configuration? Review the custom field’s “Access” subtab to see what the default access level is and if there are any special roles defined. Normally, these fields have no role and the default access level and default level for search/reporting are set to Edit.

Thanks Keith for your time in this, we are very stuck. The field access its like you said. We also ran the cache invalidation, and the error is still there. It happens before and after the LiveOrder.get The field is set in Customization > SuiteCommerce Advanced > Configuration Under Advanced > Custom Fields tab like the image

This is the correct place to put the custom field. Can you send me a screenshot of the custom transaction body field’s “Access” subtab?

Yeah sure @Keith Fetterman

Thanks. That’s the default settings. I’m at a loss to why you are getting an error. SCA out of the box supports custom transaction body fields. I have not tested a checkbox field, so maybe there are issues with that field type. You might test a text field to see if throws an error. If it doesn’t, I would file a support case. You should probably submit a support case anyway. Good luck

The same behavior with free form text. Yes I’ll probably create a case for this. Thanks Keith!

Total weirdness. Good luck