Jump to content
View in the app

A better way to browse. Learn more.

FMForums.com

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Import matches text that is not identical

Featured Replies

I have a FM DB of several thousand links of specific text on web pages created using a chrome extension (super simple highlighter).

Links created by Chrome Extension 'Super Simple Highlighter'

The links look like attached image - The initial part is identical but after the   #:~:text=   it has a distinct link pointing to a different highlighted text.

I export the links to a little program that checks if they are still there on the web and returns an error if they have changed. My little program gives me a .csv of all the URL's that had errors.

I then import that list of erroneous URL's back into my DB and this is where I run into problems.

If only one of the links in the attached image returned an error, when importing it matches with all the records that are same prior to the #:~:text= , meaning I actually have more records imported than there are in the .csv

I've tried 'Always Validate' with 'Unique Value', but that hasn't worked.

I'd happily separate the .csv file text to show just the text after the #:~:text=  and import to a calculation field showing the same... but I can't match to a calculated field. It needs to stay a calculation field because the URL is often updated.

I really thought FM imported matching identical data, what am I doing wrong?

Thanks so much in advance 

 

 

 

1 hour ago, MariaAux said:

when importing it matches with all the records that are same prior to the #:~:text= ,

That's an interesting observation, I wasn't aware of that. Apparently, the 'update matching records` option when importing relies on the index - and the index stores only the first ~100 characters of the indexed value.

 

1 hour ago, MariaAux said:

I'd happily separate the .csv file text to show just the text after the #:~:text=  and import to a calculation field showing the same... but I can't match to a calculated field.

Try making it a Text field with auto-entered calculated value (replacing existing value). 

 

Create an account or sign in to comment

Important Information

By using this site, you agree to our Terms of Use.

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.