Text Expander-Text replacement not behaving as I expect

Cyber-Wizard · Post by **Cyber-Wizard** » May 3rd, ’25, 11:51

I've been using some Text Expanders to automate the documentation of vendor invoices and receipts.
I typically enter in the date on the document by hand followed by the vendor and then the details of the receipt
EG: 2025-04-22_Vendor_-_Supply_Purchase

I have been using Text Expander to automate some of the more common types of receipts so that as i finish typing the vendor name it gets expanded to fill in the rest.
I opted in one case to use a drop down selection form to insert an entry in the receipt that is a variable.
When I use the Selection form my entire line gets replaced rather than have my text complete from where I entered the vendor name.

Using just Text Expander my entry would be completed as shown below with the expanded text in bold
2025-04-22_Jim's_Automotive_-_Vehicle_Repair

When my Text Expander has a Selection Form in it my entire line gets overwritten with the completed text up to and including my trigger string and turns out as below (With or without "Don't Delete String" enabled).
Automotive_-_[Vehicle_Name]Vehicle_Repair

The preceding date and trigger string are gone, leaving me only with the expanded text and the result of my form selection.
Should I be doing something different to permit my manually entered text to remain in place when using a Selection Form?

Post by **Tom** » May 3rd, ’25, 12:42

This should not be the case. Could you send me some screenshots of your phrase and Selection Form definition to our support email?

Cyber-Wizard · Post by **Cyber-Wizard** » May 3rd, ’25, 13:48

I figured it out.

The issue is with my document scanning software.

Focus changes from my scanning software to the Fastkeys Selection Form when it pops up. When the selection form closes focus returns to my scanning application and it automatically selects all of the text in my entry field, which Fastkeys then overwrites.

My phrase and selection form work just fine anywhere else.

It's a quirk that has frustrated me in the past.

Post by **Tom** » May 3rd, ’25, 21:30

Try adding a simulated home button at the beginning of your phrase: {Home}