kentico how to translate text to page alias

Treating Binding objects as separate tasks (LogSynchronization) There are pros and cons to both scenarios. You can have an it where an insert / update / delete triggers an update on the Parent object.You can treat the Binding object as a normal Table with 2 referencing fields, where an insert / update / delete will trigger an individual Staging task with just itself, or.There are 2 ways you can synchronize a binding object. Step 3: Manually processes the Binding Table Data.Step 2: Appending the Binding Table and Bound Object Data to the DataSet.Step 1: Trigger a Document Update When a Binding Occurs.Manually Appending Node Binding Data to the Node.Building the Staging Task Data – DataSet Creation.Building the Staging Task Data – Related Data Objects.Treating Binding objects as separate tasks (LogSynchronization).In order to have Node categories create an update for its document, and handle the staging tasks, I needed do some heavy lifting.įeel free to use the follwoing table to navigate the key components of this article: Think about it, a Page update really isn’t a 'Node' update, it’s an update on the Document pdate with Node, Versions, Related page relationships, etc, all packed into it. It seems that unlike custom-built Objects, Pages are much more complex, and thus require a custom work. I was baffled as usually if you configure a binding relationship to have a Parent type, and set the SynchronizationSettings to TouchParent, it will create an update for the parent object and include your binding relationships automatically. While I was working with the Node Categories functionality of the Relationships Extended module, I discovered that by default, if you have a Node as a Parent to your binding relationship, it doesn’t automatically stage with the page. Why an article on binding relationships on Nodes?

Kentico how to translate text to page alias