<?xml version="1.0" encoding="utf-8"?><feed xmlns="http://www.w3.org/2005/Atom"><title type="text">Blog posts by Mauro Vieira Gonçalves</title><link href="https://world.optimizely.com/blogs/mauro-vieira-goncalves/" /><updated>2020-08-05T02:31:04.0000000Z</updated><id>https://world.optimizely.com/blogs/mauro-vieira-goncalves/</id><generator uri="https://world.optimizely.com/blogs/mauro-vieira-goncalves/" version="2.0">Optimizely World</generator><entry><title>Extending Episerver Promotions with custom logic and data</title><link href="http://maurovieiragoncalves.wordpress.com/?p=176" /><id>http://maurovieiragoncalves.wordpress.com/?p=176</id><published>2020-08-05T02:18:05.0000000Z</published><updated>2020-08-05T02:31:04.0000000Z</updated><author><name>mauro.vieira@valtech.com</name></author><category term="Blog post" /><summary type="html">When it comes to promotions, Episerver provides a big set of out-of-the-box (OOTB) options in which we can rely. You can review all the OOTB types in here. But depending on the business rules and markets, some implementations may need to add custom properties and apply custom logic on top of what Episerver already provides. [&amp;#8230;]</summary></entry><entry><title>Episerver Product Recommendations and multiple carts</title><link href="http://maurovieiragoncalves.wordpress.com/?p=157" /><id>http://maurovieiragoncalves.wordpress.com/?p=157</id><published>2020-04-15T03:53:13.0000000Z</published><updated>2020-04-15T04:01:55.0000000Z</updated><author><name>mauro.vieira@valtech.com</name></author><category term="Blog post" /><summary type="html">A few days back I was bumped into an issue using Episerver Product Recommendations (formerly Episerver Perform) and multiple carts that I thought it may be useful to someone else using the same approach. We are working in a B2B implementation in which one user is able to create several carts. They can name each [&amp;#8230;]</summary></entry><entry><title>Disable Pricing and Inventory for Episerver Find</title><link href="http://maurovieiragoncalves.wordpress.com/?p=146" /><id>http://maurovieiragoncalves.wordpress.com/?p=146</id><published>2020-04-05T22:18:43.0000000Z</published><updated>2020-04-05T22:31:47.0000000Z</updated><author><name>mauro.vieira@valtech.com</name></author><category term="Blog post" /><summary type="html">In my last post we reviewed how to disable Episerver Find while we are running heavy operations on the Catalog, like an import from a PIM system. Today we will review a similar strategy, but for Pricing and Inventory and Episerver Find. It is pretty common that the Inventory APIs from Episerver are overwritten to [&amp;#8230;]</summary></entry><entry><title>Disable Episerver Find on large Commerce Catalog updates</title><link href="http://maurovieiragoncalves.wordpress.com/?p=122" /><id>http://maurovieiragoncalves.wordpress.com/?p=122</id><published>2020-03-12T02:03:39.0000000Z</published><updated>2020-04-05T22:31:47.0000000Z</updated><author><name>mauro.vieira@valtech.com</name></author><category term="Blog post" /><summary type="html">We are working in an Episerver implementation that has a huge Catalog. We have around 130.000 products, and each of those, has at least 1 variant below. Which give us around 260.000 entities. One of the challenges that we have faced, was pushing updates from the PIM platform into Episerver. With that amount of items [&amp;#8230;]</summary></entry></feed>