gonzalo.moraga wrote:I tried using the script that you posted and i got these
The input in my CSV file is fine
https://imgur.com/a/KTT80
The seach field is filled just fine, but the rows are not being filtered.
https://imgur.com/a/tBa8v
As rows are not being filtered, the script is always pressing the first 'R' button of the page.
https://imgur.com/a/UVsBS
Here is an example of how the page look when i fill the field manually
https://imgur.com/a/q0fnO
Also, if i select the field and press the 'enter' key after is filled by the script i can filter the table, but i tried my macro to do that and couldnt do it neither

OK, I understand clearly thanks to your Screenshots. I guess the Filtering takes place "on-the-fly" as you are typing the Track Nb from some background JavaScript on the Page, or indeed if you press 'Enter', but when filling in the Input Field using the 'TAG' Mode, the Page doesn't "realize" that that Field has been filled in...
You are on v8.4.4 for CR, that's good, then you need to replace the Line in your Script:
Code: Select all
TAG POS=3 TYPE=INPUT:TEXT ATTR=ID:pedido CONTENT={{!COL1}}
... with the same Action using the 'EVENT' Mode which should do the "Trick" already...
You could maybe add a mini-'WAIT' Statement (WAIT SECONDS=0.5) before the Click on the 'R' Button to allow a little bit of time for the Filtering to take place.
If that still doesn't work, you would need to add the "Actions" of selecting the Field with the Mouse (=> 'CLICK') after it has been filled in (either using your original 'TAG' Statement (which will be quicker) or with the "new" equivalent Statement in 'EVENT' Mode (which will be a bit slower as all Chars in the Track_Nb are typed one by one)) and pressing the 'Enter' Key on your Keyboard (=> 'KEYPRESS'). That should trigger and force the Filtering then... And see if the 'WAIT' Statement is still needed or not...
(The 'CLICK' Statement will have already been recorded if you use the 'EVENT' Mode to fill in the Input Field, it's not necessary to add a second one, that whole 'CLICK' Statement is actually not needed at all and can be commented out, but iMacros will automatically record it when you need to select the Field in order to be able to press the 'Enter' Key. (But it doesn't harm, you can leave it...))
Some Mechanism you could add as well to increase a bit the "Reliability" of your Script would be to use "Relative Positioning" (=> TAG POS=R1) for the Click on the 'R' Button, by first clicking on the Field for the 'Track_Nb' in the Row as Anchor, using the 'TAG' Mode. (And you then replace the 'TXT' Attribute that will be recorded with "TXT:{{!COL1}}".)
(The "R" in "TAG POS=R1" comes from "Relative", it has nothing to do with your "R" Button, it is pure Coincidence...

)
The Relative Positioning would actually already "do the Job" of selecting the correct corresponding 'R' Button if the Row was already displayed among the first 50 Results on the first Page..., even without any Filtering...
>>>
Some extra Check for some extra Reliability would be to add a Check on the "Monstrando items del 1 a la 1 de un total de 1" Result Field to then trigger a Conditional 'PROMPT' or Conditional 'PAUSE' to alert the User that stg went "wrong" and that there are (still) more than 1 Result but the Relative Positioning on the 'R' Button would probably still pick the right 'R' Button or would abort the Script if the Anchor is not found... (if you don't use '!ERRORIGNORE'...)
OK, good luck and post your Final Script...
- (F)CI(M) = (Full) Config Info (Missing): iMacros + Browser + OS (+ all 3 Versions + 'Free'/'PE').
- I don't even read the Qt if that (required) Info is not mentioned...!
- Script & URL help a lot for more "educated" Help...