IsLocalized randomly failing

Question

I have a function that localizes a Component (if needed) before updating its content. I'm randomly getting errors when, after this call, I try to update the content, getting a 'It is not possible to check-out a shared item' error. Taking a look at the logs, I see that component was not localized. The only reason is because this item.BluePrintInfo.IsLocalized is lying.

Here my code...

```

ComponentData item = (ComponentData)client.Read(tridionItemUri.ToString(), new ReadOptions());
    if (!(bool)item.BluePrintInfo.IsLocalized)
    {

        client.Localize(tridionItemUri.ToString(), new ReadOptions());
        Logger.Info(new TridionItemLog() { Message = "Component localized", Tcm = tridionItemUri.ToString() }.ToString());
    }

```

If I go to SDL Web and manually localize the Component, then I can update with no problem.

So my question is. Could this BluePrintInfo be cached or not realtime info? Should I use another way to check whether my Component is localized?

Thanks in advance.

BTW: It's SDL Web 8.5 SP1

Answer 1

With regards to your question of "Could this BluePrintInfo be cached or not realtime info?", the answer is 'No'. If there was a level of caching then this would need to be configured when multiple Content Manager servers are load balanced, and this is not the case.

I've just run the following test to verify this also (using the Core Service):

1. Create a new component in 300 level
2. Check `IsLocalized' in 300 = False
3. Check `IsLocalized' in 400 = False
4. Localise the component at 400
5. Check `IsLocalized' in 400 = True
6. Check `IsLocalized' in 700 = False
7. Promote component from 300 to 200
8. Check `IsLocalized' in 300 = False
9. Check `IsLocalized' in 400 = True
10. Check `IsLocalized' in 700 = False

This all seemed to be as expected and didn't show any signs of caching.

I see that IsLocalised is a nullable boolean. I wonder under what circumstances it is null? Maybe an SDL insider can answer that, as the CHM documentation doesn't give any info.

I also tried creating a new component and saving it but not checking it in. This created a v0.1 of the component, but this too seemed to have the correct IsLocalized value in the child publications (even when localised in the child publications).

If this error is consistently repeatable then I think you should raise it as a bug with SDL Support.

---

Update:

Are you re-reading the component (i.e. the value of item) after the localisation has taken place? If not, then you may want to tweak your code to the following:

item = Client.Localize(item.Id, new ReadOptions()) as ComponentData;

That will update the item object with the newly localised version of the component.