@Bhargavj3227 Maybe due to AutoSave Field DX component version does not match your Pega 24.1.4 runtime, so the save payload is built incorrectly and ends up targeting the wrong field (like pyDescription), which triggers the 400 error. Fix it by re-importing the Constellation UI Gallery package that is specifically meant for Pega 24.1 (the 2.x / release 2.0 line), then rebuild/publish the component again and retest. Once the correct version is used, the AutoSave component will send the proper save request for the field you configured (.Notes) and the save API will succeed.
@Sairohith After upgrading to the latest version of the component, I’m seeing a new issue: the Save API is being triggered multiple times whenever a property value changes. For instance, the Notes field appears in every assignment. On the first screen the save API fires once, on the second screen it fires twice, and on the third screen it fires three times. The number of save calls keeps increasing with each assignment. Which is resulting in Lock errors. Please I need expertise here.