I agree it needs to be fixed. But here on forum, they won't even talk to me anymore because I've been bugging (pun intended) them about it. But I DID at least beg that they make it known in Knowledge Base (even if they implied that it was intentional) so people wouldn't get repeatedly hurt by it UNTIL they get it fixed.
Thank you, FMI, for providing the article.
UPDATE: Regardless, Glitchtracker, I gave you a kudo for speaking up. I wish more people spoke up. "... and then they came for me but there was nobody left to speak up."
thi is not a *resolution*, and in my humble opinion not even a workaround, but an additional needless unacceptable amount of work.
I'm very angry too. I lost and loose a lot of credibility on a project because of it.
(It's the same problematic project as the runtime problem -- some people know about it -- you can understand how upset I am!)
It's a runtime project with import/export of 7 tables with double export (new records = import with new ids, old records = import with actualisation).
Because of this bug, the database got ruined a dozen of time (of course, before each import or export, a timestamped backup occures, but can you imagine how many hours I spent to fix this mess?).
So please, FileMaker, take example of the runtime problem and fix it ...
Because, it's quite exactly the same dimension of the problem.
Update:LaRetta edited her message quicker than I did ...
Hi, LaRetta! Don't be so sad, only oki was resolutly aggressive to you (and refused consequently to argue with me by the way, strange person), so, it's quite okay, isn't it?
I just looked for the kb.
I don't really like the way it's written ...
I miss one word in the sentence "This also affects existing Import Records script steps, as new fields are automatically added to the import order."
This word could be "erraticly" or "incomprehensibly" or perhaps it could be two "without sense" ...
I really didn't understand why the option "Arrange by: matching names" doesn't match no more.
And neither the way it mismatches (cool erratic grammatic sentence, isn't it? Maybe incomprehensible, but I hope however making sense).
Oki182 was fine ... at least s/he took the time to attempt to debate, explain and examine the issue.
I chuckled at the wording as well but whatever it takes so that, when someone searches for 'import' , it appears at the top (actually second from top) of the results and explains the problem. This bug also hurts us every day and KB isn't the final solution.
Well the recent gestures have at least given me some glimmer of hope; At least it is acknowledged now.
Hopefully this is the start of a long list of many good things to come from FMI.
Please do not make us wait too much longer for this really outstanding issue. ;)
I agree, Mr. Vodka, on all counts! SALUTE!!!!
I agree also... FMI have proved that they are listening... now all we need is further action.
They are half way there, which is a a vast improvement from previously... It sure is a glimmer of hope.