6

We have a component having below fields in the metadata:

  1. ID (Single Line Text Field)
  2. Expire Date (Date Field)
  3. Message (Single Line Text Field)

With this when we publish this component, the values goes to Broker DB as expected and after updating the values of above fields reflects in the Broker DB as well.

Now when we add another metadata field of type “Embedded Schema” and start updating the above fields, it starts behaving strange. So now after updating when I publish the component, ONLY the RECENTLY UPDATED metadata fields have values in broker, other field values become NULL or Empty. And the pattern continues in subsequent publish actions.

The Embedded Schema has fields something like below:

  1. DomID (Single Line Text Field)
  2. Medium (Keyword Field)
  3. Tag (Keyword Field)

Now If I choose any value in one(or both) of the keywords fields and publish the component, It starts behaving normal and all the values present in the Broker DB.

Any Idea guys, what could be the reason for this strange behavior?

*Just to make sure It's not related to broker caching, we will be disabling it and test the behavior. I will update the question with the results.

  • 2
    Is the same experience observed when the embedded schema doesn't contain keywords? If it is not, can you test with (a) one keyword field (b) keywords from the opposite of the existing (e.g. if categories, then if they are embedded in the schema). Sounds like something you may need Tridion Support for. – Dylan .. Mark Saunders Jan 26 '16 at 12:57
  • 1
    Is this with or without HR1? – Dylan .. Mark Saunders Jan 26 '16 at 12:59
  • It's without HR1, on the lower environments we have HR1 installed and we don't have this issue there. So it could be related to HR1. I will work on the test scenarios suggested by you and update here. – Saurabh Gangwar Jan 26 '16 at 15:56
2

The correct course of action, of course, will be to first install SP1 HR1 so environments are consistent - this will likely be the instructions from Support without having to add further hotfixes to complicate the setup (remembering that hotfixes are not supported in the context of being used with other hotfixes etc. but are provided on an 'as is' basis.

I've checked the list of hotfixes applied in HR1 and nothing seems to explicitly match the scenario described but that's not to say it isn't the solution.

  • Yeah, Installing HR1 fixed the issue. – Saurabh Gangwar Jan 29 '16 at 13:12
3

We found an answer, but it's very much a workaround.

We determined that all of the field values are saved when you select a value from a single value metadata field that is linked to a category with multiple keywords. We tried multiple iterations of this, just to confirm that this condition made it publish and that not doing this condition made it not publish.

Following that, we added a new dummy radio button field, pointed it to a category that had multiple keywords, and set one of those to be the default. That makes it work for new components. We also made sure that it had a descriptive label telling the content editor that one of the options had to be selected (since they wouldn't be populated just when you're editing). This should take care of existing components.

  • Noting, of course, if you make the new field mandatory it will break existing publishing as the field isn't populated. Options are 1) synchronize {for example using Pankaj's alchemy plugin} 2) make it optional and 'trust' editors We've gone for the latter. – Dylan .. Mark Saunders Jan 26 '16 at 19:05

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.