Hot answers tagged

3

After long investigation, I have found that it is not possible to differentiate them. The resolving is done pre-transaction-create. Also, there in the transaction object, there is no property saying that it is a "child" transaction.


2

You can use IsExistingObject to verify if the object exists, this google search shows some examples of using it: https://www.google.com/search?q=session+isexistingobject+tridion Something along these lines: if(this.Engine.GetSession().IsExistingObject(tcmUri)) { // object exists} You'd need to make sure the Tcm Uri to the object you're checking is changed ...


2

Instead of trying to do it in the constructor, I suggest using a Lazy<T> property to ensure that this configuration is only loaded once.


2

Since, you are using DXA, I will say the approach of generating the sitemap might not makes sense (unless there are other fine prints which we are not aware about). The correct approach could be similar to the one mentioned here: Generate Sitemap XML File using default functions of DXA 1.5/1.7 in Web 8/8.5


1

It depends what you need, if indeed to check whether an item exists, then it's Nuno's answer. Otherwise... I need to validate the presence of the Component in it's top Parent Publication You have a property on a Component (and other Repository Objects) which will give you the Item in the context of what you call the "top Parent Publication", see: ...


Only top voted, non community-wiki answers of a minimum length are eligible