New answers tagged

0

What you can do is change __Updated by field to a value which you know that the item doesn't have, e.g. sitecore\pse script. Sitecore will think there is a change so it will execute all the events and update statistics, and it will set the __Updated by field to the current user value, ignoring the value which you use in the script, e.g.: $item.Editing....


2

What version of Sitecore are you on? I've got the same problem with Sitecore 10.1 with a droplist field. It converts the fieldname to <fieldname>_t when querying instead of <fieldname>_s, even though the config is correct. It's not a calculated field, just a standard dynamic field. Take a look at your search log output - you can see sitecore ...


Top 50 recent answers are included