[DONE] Custom URLs are not working

🔧 Bugs & Issues
1

It used to be possible for us to formulate our own URLs and use the record ID by just having the name of the organization, then a slash, then the word record, then another slash, then the item ID of the record. However, it seems now that when these URLs are in a summary calculation field, every time you click on one of these links, in spite of the link being a good link, it always goes to the first link that’s found within the calculation field. I know that URLs just had a massive change because they look totally different now, and I knew that was coming, but did the dynamic URL option now break as a result of that change?

3 Likes
2

Hi @andrew.cranston,

thanks for reaching out and sharing your issue. Indeed, we did a rework of the record URLs to avoid the brackets in former URLs (which would lead to confusion in the past).

The custom URL format is still supported and tested:

https://tapeapp.com/ORG_SLUG/record/RECORD_ID

We just verified again that such links still work as they have in the past.

Does your issue only concern calculation fields with multiple record URLs inside?

Could you share an example output and the exact URLs that are not working?

Thanks for providing more insights!
Cheers
Tim

EDIT: We deployed a fix that should resolve the issue. Indeed, there was a problem with our parsing logic for record URLs inside calculation fields that would yield the behaviour described by @andrew.cranston inside calc fields with multiple record links. The parsing logic is designated to improve UX by detecting record URLs and navigate inside the application instead of opening a new page / loading the entire app. This speeds up things - but was not properly working in some cases with multiple record URLs inside a single calc field.

Thanks for the quick report &
Happy building
Tim

3 Likes
3

@andrew.cranston and @Tim - just another datapoint to chime in here.
We often use calculation fields that have multiple custom URL’s formatted in the way described.

A parent organization with a calculated summary table of all ‘Roof Tops’ associated with that org. This includes a custom URL utilizing the Org Slug and record ID for each of these related Roof Tops.

I just tested to confirm on our end and these custom URL’s are working fine for us at this time.

3 Likes
4

Yes I can confirm the issue is fixed. Huge thanks to @Tim and team for such a quick turnaround!

2 Likes