Puchase Order Is not creating from Source requestIssue <!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } Purchase Order is not creating from Source request. After clicking on submit nothing happens and getting the error " No sr_message value received from: ProcSourceRequestManager.processRequest" in the console tab during submission. Release<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } NA Resolution<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } The catalog item name contained a literal double-quote character (Example : 'Laptop Bag - HP 15.6" Backpack'). JSON encoding process treats it as an end of the string, trimming all data that follows. As a result, the encoded payload is incomplete and does not contain the necessary information to create a Purchase Order.Further Explanation for different scenarios :There are two different symbols: Straight Quotes (") and Smart/Curly Quotes (").Scenario 1: Straight QuoteThe client recognizes straight quotes as special JSON characters and escapes them before encoding:Client sends: {"name": "Laptop Bag - HP 15.6\" Prelude Backpack"}Server decodes: {"name": "Laptop Bag - HP 15.6\" Prelude Backpack"}JSON is valid.Scenario 2: Curly Quote + glide.ui.convert_curly_quotes = falseCurly quotes are valid inside JSON strings, so no escaping is needed. The client sends them as-is (with curly quotes):Client sends: {"name": "Laptop Bag - HP 15.6" Prelude Backpack"}Server decodes: {"name": "Laptop Bag - HP 15.6" Prelude Backpack"}JSON is valid.Scenario 3: Curly Quote + glide.ui.convert_curly_quotes = true (or unset)The client again sends the curly quote unescaped - valid JSON at send time:Client sends: {"name": "Laptop Bag - HP 15.6" Prelude Backpack"}The server converts the curly quote to a straight quote:Server decodes: {"name": "Laptop Bag - HP 15.6" Prelude Backpack"}The straight quote now breaks the JSON structure. Parsed value: {"name": "Laptop Bag - HP 15.6"}Everything after the converted quote is silently dropped, causing a data loss error.So for item Laptop Bag - HP 15.6'' Prelude Backpack it executes as Scenario 1. But for Laptop Bag - HP 15.6" Backpack it executes Scenario 3.There is a system property to handle such type of quote: glide.ui.convert_curly_quotes.Recommended way is to add glide.ui.convert_curly_quotes = false, so next time curly quotes will be processed as scenario 2 without errors.