You are nearly there. For each Links field, you have another EmbeddedSchemaField : Link
EmbeddedSchemaField links = fields["Links"] as EmbeddedSchemaField;
if (links !=null)
// This List will contain All 'Links' embeded fields: Count = 2
IList<ItemFields> linkFieldValues = links.Values;
// Get one by one each Links field
You need to add the DXAPropertyMarkup in the right place. As you are using multiple linked component field, so I will suggest you to add markup in the div immediately after the for loop -
it will be something like [Sample Code] -
@for (int i = 0; i < Model.LinkedComponent.Count; i++)
LinkedComponentModel linkedComponent = ...
As far as I know, there is no provision to allow more than one schema type on Embedded Schema Field.
But I think you can try this by modifying the source of the schema (I haven't tried this option yet).
By the way, it's not a good approach.
From my experience, I would suggest to have Component Link field which allows more than one schema type.
Unfortunately for me the problem wasn't really there.
As the included screencast shows it actually was working, but I/we didn't "get it".
At first it looks like it isn't working, because I expected to be able select it (by clicking on it) and to drag it in a different position, just like in the older Tridion versions.
But, now it turns out that it is a ...
As @Frank mentioned in his comment, please explain the issue being more specific.
But the first thing you should do is, check the browser settings according to the link below:
Configuring your Web browser for Content Manager Explorer (Login Required)
you can also find it in the user manual doc.
I am not clear about your Dynamic Component Templates, So I am trying to answer the question generally.
So to publish a binary from a CT, we need to ensure two things in templating:
The binary is being added to the package.
Publish the binary from the package.
To add a binary to the package, we use AddBinary() methods. Which are described quite well here.
Not as far as I know but I guess one approach would be to add all the fields to a single embedded schema and then instruct users to use the correct fields based on the type - the type being determined by a drop down field.
You could take it one step further with a GUI extension to hide the fields based on a naming convention e.g. if the value of the first ...
Definitely, there is a way to achieve this, but before you do that change you need to be very careful about your data. I will suggest while doing that change in the lower environment analyze it properly and then only go ahead -
Here are the steps -
You need to update the Root Element Name of the Embeddable Schema that you're using.
You need to update the ...
Content Types in Experience Manager would be one way to create this kind of default content values. This is where you can create one or more Custom Content Types that set default details for new content created in Experience Manager at a given Publication.
If the product were to add these kinds of flexible defaults it'd likely rely on Content Types and the ...
We found the root cause for the issue.
The problem was in the way the our custom module was initialized. Namely, the SemanticMapper was not called on the model inside Emerald module. We added the necessary code to registerEntitites() in the EmeraldInitializer class.
@ModuleInfo(name = "Emerald module", ...
You can try in the following way. Not sure if i got you correctly, but seems you want to parse the schema filed nodes, not from any component with value in the fields.
Load Schema Details first,
SchemaFieldsData schemaFieldsData = _coreServiceClient.ReadSchemaFields(schemaId, false, null);
Then, search for the embedded fields using the following:
Show / hide logic in Tridion Schemas?
A text fields that uses a Category (with nested Keywords presented with the Tree option) is probably the closest thing we have in Tridion that presents additional options after a user selects an initial option. But this only works for selections.
Separate Schemas Rather than Component Links
For two Schemas with ...