I had a site whereby there were around 2400 editorial contents. Out of those 2400 contents, only 1000 contents had a proper tagging and proper values for the profile keys. In order to update all those profile keys, I had to write a code to update those content.
Recently, I had a request from the client to provide him with the list of profile cards that were used to tag contents. Again Sitecore Powershell is here to rescue. I sat and it took me around 15 minutes to write up and test the script. In this small article, I will share the script I have written and also, how you can customize it for your own requirement.
Sitecore powershell has changed my day to day work. Changing datasource, extracting data or creates items in Sitecore using SPE can be performed in seconds by just writing up the scripts and run it. I had a requirement whereby I need to dynamically show the user a UI which is rendered dynamically based on his input.
I have been writing articles about how to aggregate data from MongoDB to Sitecore SQL Reporting database. But it new occurred to me that I can also have some of my data to be added to the Sitecore Analytics Index. For this article today, I will be explaining on how you can add custom data to the Sitecore Analytics Index. I’ll take the following scenario.
Personalized contents are everywhere now. In order to drive more sales or show the best contents to users, marketers define strategies on to allow users to be exposed to contents or offers which are meant for them. I had a requirement where I had to track the user content flow on one of our sites.
From my last few posts, I have been talking about the Sitecore Tasks. Using the Sitecore Tasks allow a user to either set the task as synchronous or asynchronous. It is the
Sitecore.Tasks.DatabaseAgent which runs at a define interval and loops through the container
Following recent Sitecore versions, we have seen that Sitecore has integrated the Job.aspx page which is found under the admin folder. This is very useful to content authors, developers because it helps to see what current tasks are being executed. However, for me, I see a missing feature: Who has triggered that task?