NAV 2013 R2 keys

Rob_Hansen

The ability to sort by any column on lists in NAV 2013 R2 is great...but is there no way for the user to select a key or define multiple sort columns? Example...I want to sort the sales order list by (assuming a key exists) "Location Code,Requested Delivery Date". Is this no longer possible without it being handled through C/AL code?

Marije_Brummel

I thought you could hold down the CRTL key while click on columns to sort on multiple fields.

tinoruijs

Mark Brummel wrote:

I thought you could hold down the CRTL key while click on columns to sort on multiple fields.

You have to use SHIFT.

Marije_Brummel

Ah, thanks Tino.

mdPartnerNL

that's a nice option in 2013. Positive

Rob_Hansen

Thanks guys - learned my new 2013 R2 thing for today!

Wortha

Thanks all. This one had me frustrated as well.

PKey

Hello,
please how can I cancel sorting by colmun to the default sorting by unview colmun except reopen page?

cyuwono

The shift key works great ! but is there a way to sort a column in ascending order and another column in descending order?

jglathe

Hi,

took me a while to notice it... I know I'm like a hunter from the stone age before a computer when RTC is running, but... Riiight. There really seems to be no way to select* a predefined key in a page, because the "Sorting:" control is missing. In NAV2013 it's there, in NAV2013R2 it's missing. Just to be sure I checked two builds. How sick is that? I mean really, WTF? And now we enable metrics to remove the last useful pieces of the UI, or how do I understand it? ](*,)

with best regards

Jens

* other than setting it in the designer, or C/AL

tinoruijs

jglathe wrote:

How sick is that? I mean really, WTF?

I don't think it's sick. I think it's better. I can count on 1 hand how many users use the key-select-button in the classic client.
The solution now is more user-friendly.
And a user can save a customized page in their rolecenter to save the selected sorting on a table.
Great improvement!

jglathe

Hi,

tinoruijs wrote:

Great improvement!

This may all be very well, but why remove the other feature? When you even don't save any screen space? And I know I belong to a dying breed, but somebody has to debug the fscking thing. Or do they think we're all using T-SQL for debugging purposes, because it's so "user-friendly"?

with best regards

Jens

tinoruijs

How does this change effect your debugging?

jglathe

Hi Tino,

I use the available keys of a table quite often when I'm on the hunt for an error.

with best regards

Jens

cyuwono

How do we know which key is active once the user change the sorting field ?

Carlos

jglathe

Hi Carlos,

cyuwono wrote:

How do we know which key is active once the user change the sorting field ?
Carlos

that's one of the problems. Answer: The one selected by the user, even if it doesn't exist on the table. But you also have a problem finding out what the primary key is... no list of keys. For the common tables this is no problem, but there are many (especially in AddOns) where I don't know them immediately. So... you will need a Development Environment for this.

with best regards

Jens

alex9

jglathe wrote:

Hi Carlos,

cyuwono wrote:

How do we know which key is active once the user change the sorting field ?
Carlos

that's one of the problems. Answer: The one selected by the user, even if it doesn't exist on the table. But you also have a problem finding out what the primary key is... no list of keys. For the common tables this is no problem, but there are many (especially in AddOns) where I don't know them immediately. So... you will need a Development Environment for this.

with best regards

Jens

I completely agree with Jens. That's all just ridiculous. That sorting by predefined key feature is used everyday. And now it's gone. MS just have no idea how everyday development is being done.

mdPartnerNL

I agree with your statement but isn't the reason this option is gone is because SQL chooses the best key anyway? Whatever the user would have chosen..

jglathe

mdPartnerNL wrote:

I agree with your statement but isn't the reason this option is gone is because SQL chooses the best key anyway? Whatever the user would have chosen..

That's the case for a few releases now (since 5.0?). But why should I need to remove the keys feature? You need it for certain processing tasks (order the line items by a predefined key, and switching between several predefined keys). That's what the business process requires, and the application should comply. What the backend database makes of this doesn't really matter, as long as the application does what is required. But removing the ability to select a predefined key is not good.

with best regards

Jens

mdPartnerNL

Yes, I forgot that part.

Whatever SQL choose you want it sorted on a defines key structure and not on 1 column.

So this option is missing and this is bad ms!!

Your only option is to add some dropdown with keys on the page itself...

jglathe

mdPartnerNL wrote:

Your only option is to add some dropdown with keys on the page itself...

... and what control would this be in the page designer?