@Aaron McCausland That's correct, Search Rebuild Index should be executed to update the items in Webstore.

@Aaron McCausland Yes, you may test the changes without Search Index. However, you need to execute Cache Invalidation Request then use Google Chrome Guest Browser to avoid caching.

Hi @Aaron McCausland That's good to hear that the item is now visible. Thank you for the update.

@Aaron McCausland Coordinate with the support who handles your case. Thank you.

Hi @Aaron McCausland Mentioned that 500 error encountered might be related to the PCV. On our end we can't continue to investigate and give a solution if there's no case for a specific concern since we can't check the the account implementation.

@Aaron McCausland As much as I would like to help, I can't give an accurate solution if I can't check the configuration implemented on your end. Moving forward, I would suggest to review the SuiteAnswer Article below regarding Setting Up Personalized Catalog Views then check the steps you have executed when Customer and…

@Aaron McCausland It would be best to create a case regarding on your concern since we need to gather and check the information listed below so that we could give you an accurate solution. *Configuration of Customer segments *Configuration of Item segments *Personalized Catalog Views feature *Shopper Roles and Permissions

@JPrice That's good to hear. thank you for sharing the solution.

@JPrice Its not a known issue rather might be an error due to customization. If the problem is reproducible using a Standard Theme, kindly file a case so that support can check if there's a need to file a defect regarding on the affected Standard Theme. Thank you.

@JPrice If the TPL error is not reproducible using a Standard Theme then we can't investigate the problem. Please do note that it is out of scope for the support to troubleshoot any Custom Implementation.

@JPrice Try to fulfill the TPL files then deploy it on dummy domain. If the suggested solution will not be able to fix the problem, It would be best to coordinate to your AMO since we do have a separate group that specialize in troubleshooting Customization.

@JPrice If the theme is a Custom and there's an error when activating the Theme, It should be fix by your developer. Troubleshooting Custom Theme/Extensions is out of scope for support that's why NS support mentioned that you should coordinate with your developer since support might break some functionality of the webstore…

@JPrice Any changes on the customization should be discuss on the case created so that support can track all the changes implemented on your account. As much as I would like to help, I can't check or give a solution to a customization. It would be best to coordinate with your AMO for PS services if you don't have a…

@JPrice If the support that handles the case mentioned you need to coordinate with your AMO, the problem might be related to your customization. Given that scenario as much as I would like to help, Customization should be fix by developer who created/implemented the custom code/script.

@JPrice Let's continue the discussion of the encountered error on the created case since support needed the case to check your account.

@JPrice Is the encountered error reproducible using updated SuiteCommerce Theme(Manor,Posh and Base etc.)?, If no it would be best to create a case for this concern since it will need an in-depth investigation due to we need to check the code and path of the missing record.

Hi @Shubham_Singh The error encountered might be related to the Role used that don't have a permission on a workflow, custom field or custom script implemented on the webstore. Also, check if the encountered behavior is reproducible using Standard Customer Center Role, If yes, kindly create a case so that we could check…

Hi @Shubham_Singh May we know if the SuitePromotion was activated before creating the Sales Order?

@Shubham_Singh Credit Card fields are not displaying due to the selected credit doesn't required a Payment Method. By default CC fields will automatically display if the credit have a required Payment Method. There's no out of the box webstore feature that will uncheck Payment#PYMT7147, It's either process first the…

Hi @User_9VL6Z It would be best to coordinate this to the developer that implemented your Meta Analytics since the concern will fall down into customization. Thank you.

Hi @KennyT It would be best to file a case so that we could check what trigger/s different error messages based on the scenario executed. Also, we will able to locate where it was used and if it's possible to re-use the error message. Thank you.

Hi @KennyT Customize Web Site Text page is divided into subtabs for each block of text that appears in your website(Headings, Field Labels, Alerts, List Options, Buttons and Error Message). Please see SuiteAnswer Article below for your reference. Topic: Customizing Website Text ID: 30591 Topic: Using Web Site Text Groups…

Hi @RajeshaJagadeesh Got it. It would be best to create a case If you need assistance regarding on the encountered behavior since deactivating custom extension is not feasible on your end.

@User_UCDAW Did you use URL "http://<DOMAIN_NAME>/c.<ACCOUNT_ID>/<SSP_APPLICATION>/shopping-local.ssp" when checking the code changes?, Please see SuiteAnswer Article for reference. Article: Test an Extension on a Local Server ID: 71015

@User_AK77U If the encountered problem is still reproducible after using SSP SRC + Base Theme + Deactivate Custom Extension, It would be best to file a case so that support can check the registered logs on the backend. Also, each account has a different implementation and the fix on the other may not work on your end.

Hi @Shubham_Singh This might be related to role permission assigned to the newly created account. It would be best to create a case for this concern since this will need a deep investigation.

Hi @katherine_15328 User can Show Cookie Consent Banner on the webstore by activating it under Website Setup > Setup > Cookie Law Compliance. You may create a HTML file that will execute the accept/reject cookie. However creating the html file will fall down in to customization.

@User_3F3F3 . Installing different version/s of SuiteCommerce Advanced will not affect the implemented SCA version of the webstore. It will only affect the existing implementation if you will change the Touch Points set to the Domain.

@ImeldaSanchez It would be best to file a case for this concern since this needs a deep investigation so that we could check on how the content was created and if there's a problem that will arise on the webstore after hiding/deleting the content.

@eleran It's okay If feature has been enabled on your end. Regarding on the bundle access problem, You need to create a case since we will be requesting a bundle access for your account.