Greetings.

I am trying to find out the default parameter for sorting of MCMS posting.
We need to use the first posting as the default for each channel, so we have
sorted the postings in the channels to start with.

Now if we add a new posting, it will come in the first place in the sorted
order. We have noticed if we have 5 or 6 posting in the channel, it adds
after 5th or 6th position or so. In most of the cases we had more than 6
posting in a channel to start with; so that was sort of work around as newly
added posting did not change our default posting position.

Now we found that if we change the name of the posting; the sorting order
gets affected; it comes always in the first; so far my observation the
default sorting is not using
·	the page name
·	the display name
·	creation date
·	last modified date
·	published date???
Or I am missing something?

Any help is really appreciated.
Best Regards.

[ Post a follow-up to this message ]

Hi DG,

the default sorting is random. There is no obvious rule as it uses an
internal hash value.
So it is not predictable which posting is the first from API if you don't
set it.

Either set the SortOrdinal in a workflow event to the number of posting in
the channel or set the default posting name of the channel to the posting
name.

Cheers,
Stefan.

--
This posting is provided "AS IS" with no warranties, and confers no rights.

MCMS FAQ:
http://download.microsoft.com/downl...>
MCMS+2002+-+(complete)+FAQ.htm
MCMS Blog: http://blogs.msdn.com/stefan_gossner/category/4983.aspx
MCMS Sample Code:
http://www.gotdotnet.com/community/...nagement+Server
MCMS Whitepapers and other docs:
http://blogs.msdn.com/stefan_gossne...2/07/41859.aspx
--------------------------------


"DG" <DG@discussions.microsoft.com> wrote in message
news:CBDCC389-F4F1-4DB6-984A-9FC5BAE9DD7D@microsoft.com...
> Greetings.
>
>  I am trying to find out the default parameter for sorting of MCMS
posting.
> We need to use the first posting as the default for each channel, so we
have
> sorted the postings in the channels to start with.
>
> Now if we add a new posting, it will come in the first place in the sorted
> order. We have noticed if we have 5 or 6 posting in the channel, it adds
> after 5th or 6th position or so. In most of the cases we had more than 6
> posting in a channel to start with; so that was sort of work around as
newly
> added posting did not change our default posting position.
>
> Now we found that if we change the name of the posting; the sorting order
> gets affected; it comes always in the first; so far my observation the
> default sorting is not using
> · the page name
> · the display name
> · creation date
> · last modified date
> · published date???
> Or I am missing something?
>
> Any help is really appreciated.
> Best Regards.
>

[ Post a follow-up to this message ]

Thank you Stefan. But then we can not change the page name for the default
Page for each channel. We want to keep that flexible; As if author changes
the displa y name only and not page name it is little hard to do the admin
activity at the Site Manager where all page name is being used. And to type
manually for all the channel to set their default page would be lot of work
too, specially with the possibility of type o. Is it possible to automate
each channel default posting to tie to an URL? Then we can browse to that
MCMS posting and get the URL or GUID.

I always appreciate the prompt help in this news group.

"Stefan [MSFT]" wrote:

> Hi DG,
>
> the default sorting is random. There is no obvious rule as it uses an
> internal hash value.
> So it is not predictable which posting is the first from API if you don't
> set it.
>
> Either set the SortOrdinal in a workflow event to the number of posting in
> the channel or set the default posting name of the channel to the posting
> name.
>
> Cheers,
> Stefan.
>
> --
> This posting is provided "AS IS" with no warranties, and confers no rights
.
>
> MCMS FAQ:
> http://download.microsoft.com/downl...
a/MCMS+2002+-+(complete)+FAQ.htm
> MCMS Blog: http://blogs.msdn.com/stefan_gossner/category/4983.aspx
> MCMS Sample Code:
> http://www.gotdotnet.com/community/...nagement+Server
> MCMS Whitepapers and other docs:
> http://blogs.msdn.com/stefan_gossne...2/07/41859.aspx
> --------------------------------
>
>
> "DG" <DG@discussions.microsoft.com> wrote in message
> news:CBDCC389-F4F1-4DB6-984A-9FC5BAE9DD7D@microsoft.com... 
> posting. 
> have 
> newly 
>
>
>

[ Post a follow-up to this message ]

Hi DG,

I indicated that you should do this in a workflow event.
Here it is automatically done and no user interaction and no SiteManager is
required.

Cheers,
Stefan.

--
This posting is provided "AS IS" with no warranties, and confers no rights.

MCMS FAQ:
http://download.microsoft.com/downl...>
MCMS+2002+-+(complete)+FAQ.htm
MCMS Blog: http://blogs.msdn.com/stefan_gossner/category/4983.aspx
MCMS Sample Code:
http://www.gotdotnet.com/community/...nagement+Server
MCMS Whitepapers and other docs:
http://blogs.msdn.com/stefan_gossne...2/07/41859.aspx
--------------------------------


"DG" <DG@discussions.microsoft.com> wrote in message
news:A2D1AAE4-031E-4C78-9A0B-7EF64A331069@microsoft.com...
> Thank you Stefan. But then we can not change the page name for the default
> Page for each channel. We want to keep that flexible; As if author changes
> the displa y name only and not page name it is little hard to do the admin
> activity at the Site Manager where all page name is being used. And to
type
> manually for all the channel to set their default page would be lot of
work[vbcol=seagreen]
> too, specially with the possibility of type o. Is it possible to automate
> each channel default posting to tie to an URL? Then we can browse to that
> MCMS posting and get the URL or GUID.
>
> I always appreciate the prompt help in this news group.
>
> "Stefan [MSFT]" wrote:
> 
don't[vbcol=seagreen] 
in[vbcol=seagreen] 
posting[vbcol=seagreen] 
rights.[vbcol=seagreen] 
http://download.microsoft.com/downl...
+Server[vbcol=seagreen] 
we[vbcol=seagreen] 
sorted[vbcol=seagreen] 
adds[vbcol=seagreen] 
6[vbcol=seagreen] 
order[vbcol=seagreen] 

[ Post a follow-up to this message ]