Sorting inherited template fields Planned maintenance scheduled April 23, 2019 at 23:30 UTC (7:30pm US/Eastern) Announcing the arrival of Valued Associate #679: Cesar Manara Unicorn Meta Zoo #1: Why another podcast?SXA: Add custom slide template to CarouselSitecore SXA Search Result Sorting by dateSXA Search SortingSort SXA search results by date without SXA sorting renderingHow to configure SXA Search Box to search based on Fields of a certain template?Sitecore SXA Access Template fields inside a Variant Nvelocity templateSorting search results with multiple facetsMissing or presenting body-tag placeholder in SXARendering cloning | item fields are not as per their templateDisplay list of items with a dynamic query set by content editors
How to align enumerate environment inside description environment
Sally's older brother
My mentor says to set image to Fine instead of RAW — how is this different from JPG?
The test team as an enemy of development? And how can this be avoided?
Printing attributes of selection in ArcPy?
Found this skink in my tomato plant bucket. Is he trapped? Or could he leave if he wanted?
Simple Line in LaTeX Help!
What does it mean that physics no longer uses mechanical models to describe phenomena?
How were pictures turned from film to a big picture in a picture frame before digital scanning?
Delete free apps from library
I got rid of Mac OSX and replaced it with linux but now I can't change it back to OSX or windows
Resize vertical bars (absolute-value symbols)
Random body shuffle every night—can we still function?
What is the difference between a "ranged attack" and a "ranged weapon attack"?
What would you call this weird metallic apparatus that allows you to lift people?
What does 丫 mean? 丫是什么意思？
Is there public access to the Meteor Crater in Arizona?
Simple HTTP Server
How to change the tick of the color bar legend to black
Where is the Next Backup Size entry on iOS 12?
Why are vacuum tubes still used in amateur radios?
Nose gear failure in single prop aircraft: belly landing or nose-gear up landing?
Co-worker has annoying ringtone
Is multiple magic items in one inherently imbalanced?
Sorting inherited template fields
Planned maintenance scheduled April 23, 2019 at 23:30 UTC (7:30pm US/Eastern)
Announcing the arrival of Valued Associate #679: Cesar Manara
Unicorn Meta Zoo #1: Why another podcast?SXA: Add custom slide template to CarouselSitecore SXA Search Result Sorting by dateSXA Search SortingSort SXA search results by date without SXA sorting renderingHow to configure SXA Search Box to search based on Fields of a certain template?Sitecore SXA Access Template fields inside a Variant Nvelocity templateSorting search results with multiple facetsMissing or presenting body-tag placeholder in SXARendering cloning | item fields are not as per their templateDisplay list of items with a dynamic query set by content editors
I have a page template inheriting from base templates.
But when I go to edit those from Experience Accelerator, Page metadata, Other dialog, they are in a strange order. It seems like its grabbing the first item from each template, then the second item from each template and so on... but not in the displayed template order above.
I tried applying sort order but that only applies to the content editor tree - it has no impact on this dialog at all.
I want each block of fields below to remain as a block together, so it makes more sense when editing.
Using Sitecore 9.1 and SXA 1.8.
sxa
asked Apr 15 at 5:20
JenJen
273112
add a comment |
I have a page template inheriting from base templates.
But when I go to edit those from Experience Accelerator, Page metadata, Other dialog, they are in a strange order. It seems like its grabbing the first item from each template, then the second item from each template and so on... but not in the displayed template order above.
I tried applying sort order but that only applies to the content editor tree - it has no impact on this dialog at all.
I want each block of fields below to remain as a block together, so it makes more sense when editing.
Using Sitecore 9.1 and SXA 1.8.
sxa
asked Apr 15 at 5:20
JenJen
273112
You need to use different section names.List,PairandLinksfor instance, instead ofContent.
– Mark Cassidy♦
Apr 15 at 5:24
@MarkCassidy Ah - great thanks :) Feel free to post as a proper answer so I can accept.
– Jen
Apr 15 at 5:26
add a comment |
I have a page template inheriting from base templates.
But when I go to edit those from Experience Accelerator, Page metadata, Other dialog, they are in a strange order. It seems like its grabbing the first item from each template, then the second item from each template and so on... but not in the displayed template order above.
I tried applying sort order but that only applies to the content editor tree - it has no impact on this dialog at all.
I want each block of fields below to remain as a block together, so it makes more sense when editing.
Using Sitecore 9.1 and SXA 1.8.
sxa
asked Apr 15 at 5:20
JenJen
273112
I have a page template inheriting from base templates.
But when I go to edit those from Experience Accelerator, Page metadata, Other dialog, they are in a strange order. It seems like its grabbing the first item from each template, then the second item from each template and so on... but not in the displayed template order above.
I tried applying sort order but that only applies to the content editor tree - it has no impact on this dialog at all.
I want each block of fields below to remain as a block together, so it makes more sense when editing.
Using Sitecore 9.1 and SXA 1.8.
sxa
sxa
asked Apr 15 at 5:20
JenJen
273112
asked Apr 15 at 5:20
JenJen
273112
asked Apr 15 at 5:20
JenJen
273112
asked Apr 15 at 5:20
JenJen
273112
asked Apr 15 at 5:20
JenJen
273112
273112
You need to use different section names.List,PairandLinksfor instance, instead ofContent.
– Mark Cassidy♦
Apr 15 at 5:24
@MarkCassidy Ah - great thanks :) Feel free to post as a proper answer so I can accept.
– Jen
Apr 15 at 5:26
add a comment |
You need to use different section names.List,PairandLinksfor instance, instead ofContent.
– Mark Cassidy♦
Apr 15 at 5:24
@MarkCassidy Ah - great thanks :) Feel free to post as a proper answer so I can accept.
– Jen
Apr 15 at 5:26
You need to use different section names.
List, Pair and Links for instance, instead of Content.– Mark Cassidy♦
Apr 15 at 5:24
You need to use different section names.
List, Pair and Links for instance, instead of Content.– Mark Cassidy♦
Apr 15 at 5:24
@MarkCassidy Ah - great thanks :) Feel free to post as a proper answer so I can accept.
– Jen
Apr 15 at 5:26
@MarkCassidy Ah - great thanks :) Feel free to post as a proper answer so I can accept.
– Jen
Apr 15 at 5:26
add a comment |
1 Answer
1
active
oldest
votes
This dialogue is not the most flexible of sorts. But what happens is, it shows an aggregate of your templates and their fields, with little way of controlling the order they appear in.
One thing you can do however, is organise the fields under different section names. You currently use Content for all of them, meaning all the fields will end up in the same grouping.
By organising the fields differently, e.g. use List, Pair, and Links, as section names - this dialogue will organise the fields more to your liking I believe.
And yes, you can use the __Sort order on the section items to control the order of how these sections appear in the dialogue as well.
Additional Reference: Field Ordering When Inheriting Sitecore Templates
Edited to add
I actually think you can sort all of the fields even if you remain in the same section name. But you would need to manipulate the __SortOrder of the fields directly. So on the fields under one template, you set their sort order to 10, 20, 30 and so on. In the next template, to 100, 200, 300 etc. And so on. Generally Sitecore would respect the overall sort order - this is why it's "interleaving" the fields to begin with.
That said, I think it's easier to just group by different section names. That's one of the only reason sections exist, after all.
answered Apr 15 at 5:32
Mark Cassidy♦Mark Cassidy
17.5k53782
add a comment |
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "664"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsitecore.stackexchange.com%2fquestions%2f18113%2fsorting-inherited-template-fields%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
This dialogue is not the most flexible of sorts. But what happens is, it shows an aggregate of your templates and their fields, with little way of controlling the order they appear in.
One thing you can do however, is organise the fields under different section names. You currently use Content for all of them, meaning all the fields will end up in the same grouping.
By organising the fields differently, e.g. use List, Pair, and Links, as section names - this dialogue will organise the fields more to your liking I believe.
And yes, you can use the __Sort order on the section items to control the order of how these sections appear in the dialogue as well.
Additional Reference: Field Ordering When Inheriting Sitecore Templates
Edited to add
I actually think you can sort all of the fields even if you remain in the same section name. But you would need to manipulate the __SortOrder of the fields directly. So on the fields under one template, you set their sort order to 10, 20, 30 and so on. In the next template, to 100, 200, 300 etc. And so on. Generally Sitecore would respect the overall sort order - this is why it's "interleaving" the fields to begin with.
That said, I think it's easier to just group by different section names. That's one of the only reason sections exist, after all.
answered Apr 15 at 5:32
Mark Cassidy♦Mark Cassidy
17.5k53782
add a comment |
This dialogue is not the most flexible of sorts. But what happens is, it shows an aggregate of your templates and their fields, with little way of controlling the order they appear in.
One thing you can do however, is organise the fields under different section names. You currently use Content for all of them, meaning all the fields will end up in the same grouping.
By organising the fields differently, e.g. use List, Pair, and Links, as section names - this dialogue will organise the fields more to your liking I believe.
And yes, you can use the __Sort order on the section items to control the order of how these sections appear in the dialogue as well.
Additional Reference: Field Ordering When Inheriting Sitecore Templates
Edited to add
I actually think you can sort all of the fields even if you remain in the same section name. But you would need to manipulate the __SortOrder of the fields directly. So on the fields under one template, you set their sort order to 10, 20, 30 and so on. In the next template, to 100, 200, 300 etc. And so on. Generally Sitecore would respect the overall sort order - this is why it's "interleaving" the fields to begin with.
That said, I think it's easier to just group by different section names. That's one of the only reason sections exist, after all.
answered Apr 15 at 5:32
Mark Cassidy♦Mark Cassidy
17.5k53782
add a comment |
This dialogue is not the most flexible of sorts. But what happens is, it shows an aggregate of your templates and their fields, with little way of controlling the order they appear in.
One thing you can do however, is organise the fields under different section names. You currently use Content for all of them, meaning all the fields will end up in the same grouping.
By organising the fields differently, e.g. use List, Pair, and Links, as section names - this dialogue will organise the fields more to your liking I believe.
And yes, you can use the __Sort order on the section items to control the order of how these sections appear in the dialogue as well.
Additional Reference: Field Ordering When Inheriting Sitecore Templates
Edited to add
I actually think you can sort all of the fields even if you remain in the same section name. But you would need to manipulate the __SortOrder of the fields directly. So on the fields under one template, you set their sort order to 10, 20, 30 and so on. In the next template, to 100, 200, 300 etc. And so on. Generally Sitecore would respect the overall sort order - this is why it's "interleaving" the fields to begin with.
That said, I think it's easier to just group by different section names. That's one of the only reason sections exist, after all.
answered Apr 15 at 5:32
Mark Cassidy♦Mark Cassidy
17.5k53782
This dialogue is not the most flexible of sorts. But what happens is, it shows an aggregate of your templates and their fields, with little way of controlling the order they appear in.
One thing you can do however, is organise the fields under different section names. You currently use Content for all of them, meaning all the fields will end up in the same grouping.
By organising the fields differently, e.g. use List, Pair, and Links, as section names - this dialogue will organise the fields more to your liking I believe.
And yes, you can use the __Sort order on the section items to control the order of how these sections appear in the dialogue as well.
Additional Reference: Field Ordering When Inheriting Sitecore Templates
Edited to add
I actually think you can sort all of the fields even if you remain in the same section name. But you would need to manipulate the __SortOrder of the fields directly. So on the fields under one template, you set their sort order to 10, 20, 30 and so on. In the next template, to 100, 200, 300 etc. And so on. Generally Sitecore would respect the overall sort order - this is why it's "interleaving" the fields to begin with.
That said, I think it's easier to just group by different section names. That's one of the only reason sections exist, after all.
answered Apr 15 at 5:32
Mark Cassidy♦Mark Cassidy
17.5k53782
edited Apr 15 at 13:36
answered Apr 15 at 5:32
Mark Cassidy♦Mark Cassidy
17.5k53782
answered Apr 15 at 5:32
Mark Cassidy♦Mark Cassidy
17.5k53782
answered Apr 15 at 5:32
Mark Cassidy♦Mark Cassidy
17.5k53782
17.5k53782
add a comment |
add a comment |
Thanks for contributing an answer to Sitecore Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsitecore.stackexchange.com%2fquestions%2f18113%2fsorting-inherited-template-fields%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
You need to use different section names.
List,PairandLinksfor instance, instead ofContent.– Mark Cassidy♦
Apr 15 at 5:24
@MarkCassidy Ah - great thanks :) Feel free to post as a proper answer so I can accept.
– Jen
Apr 15 at 5:26