Customer Portal Reference Column Truncating value

[Martyn Houghton]

When viewing requests in the Customer Portal. the request reference value is truncated, when you have a prefix longer than two characters.

We are using a five character prefix in order to identify our references as specific to our system, as we predominately provide services to external customers, whom use systems of their own with the default IN, SR etc. The format we are using is IDX for Idox and then the standard prefix of IN, SR. i.e. incident reference IDXIN00001024.

At the moment the portal will strip the last two numbers off, as it seems to be hard coded to 10 character limit on the display column.

Cheers

Martyn

[Guest Chaz]

Hi Martyn,

thanks for reporting this, I've found the issue and added a fix, so look out for it in our release notes.

[Martyn Houghton]

Thanks for the quick response.

Cheers

Martyn

[Martyn Houghton]

@cchana

This issue has re-appeared, but now on the My Organisation Request screen. Viewing My Requests is fine

 

Viewing on My Organisation Requests truncates the last number off again.

 

 

Cheers

Martyn

[Guest Chaz]

@Martyn Houghton sadly, the number of columns will dictate how big each field is going to be. Even if we were to make it big enough for this case, it wouldn't be big enough for everyone or obscure other content. We're looking to replace this list with another type in the near future which will hopefully help. I will let the dev team know that this has come again in case there is a quick fix we can apply.

[Alex8000]

Hi @cchana, 

We are also running into some problems regarding truncation of records on the customer portal.
The red boxes in this image show all truncated records:

The Service and Status ones are only missing one character. The other ones are not essential.

Is there a way to hide certain columns to guarantee that others will be displayed properly?

Thanks,

Alex

[Martyn Houghton]

@cchana

As a short term fix I think we could live with the Summary/Overzicht column not being as wide by a few characters. Would that work for you @Alex8000?

Cheers

Martyn

[Alex8000]

Hi @Martyn Houghton,

We'd be OK with that as a short term fix. We only need space for two more characters, one for the Status and one for the Service column. With you needing three more for the reference column that would mean that the Summary column would be truncated by 5 characters?

[Martyn Houghton]

@Alex8000

Though our reference field is three characters longer the display is only truncating the last digit of, if we went for 1 character more on Reference, Status and Service, as a short term solution that would hopefully work for use both. @cchana is that possible?

Cheers

Martyn

[Guest Chaz]

This was looked at yesterday, the field will be much larger and now handle around 15 characters. You'll see the changes in 2.36

[Martyn Houghton]

@cchana

Thanks, any approx timeline on 2.36?

Cheers

Martyn

[Alex8000]

Hi @cchana,

Just to be sure, which field(s) can now handle 15 characters? Will this also help us with the Status and Service colums?

Thanks,

Alex

[Guest Chaz]

@Martyn Houghton aiming for Monday morning 

@Alex8000 I'll confirm and reply if I'm wrong but should just be the reference field which will now be wide enough for 15 characters. I'll check with the developers to see if we can do something for the status and service columns, but the later is likely to always be a problem if you have really long service names as it would then eat into the space reserved for the summary of a request.