Timeline for IsLocalized randomly failing
Current License: CC BY-SA 4.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 19, 2020 at 12:03 | comment | added | Xavier Casals | Hi. Answering to your update. I will reload the component data when localizing, that seams to be a good practice to ensure I have the latest info, but that don't solve my main issue. My real problem is that tridion says it is actually localized, so I skip (out of the 'if then') the Localize call. I have to make an effort and find a pattern in this error. But remember Murphy laws, this is only happening in a client production environment, not in dev and not in my own environment... Thank you. | |
| Jan 16, 2020 at 14:57 | comment | added | Jonathan Williams | That's really useful to know. Thanks Rick. 👍 | |
| Jan 16, 2020 at 14:45 | comment | added | Rick Pannekoek |
In general, all properties of Core Service Data Objects are nullable, because objects can be partially loaded. This happens in particular when you are getting a list of objects. When retrieving an object through the Read method, it should be fully loaded, so no properties should be null.
|
|
| Jan 16, 2020 at 14:15 | comment | added | Jonathan Williams | No problem. I've added a small update to my answer. | |
| Jan 16, 2020 at 14:15 | history | edited | Jonathan Williams | CC BY-SA 4.0 |
added 362 characters in body
|
| Jan 16, 2020 at 14:06 | comment | added | Xavier Casals | Thank you for your time on doing this test. That nullable bool should mean something. And maybe my code is failing there. I cannot raise a bug with SDL yet as I cannot see or understand under what circunstances this is failing. I don't want to report a bug when there is a 99% that the bug it's in my code ;) Let's see if somebody tell us what the 'null' value is. Thanks again | |
| Jan 16, 2020 at 13:53 | history | answered | Jonathan Williams | CC BY-SA 4.0 |