I am still very amateur on Filemaker so i hope my question does make any sense.
I am trying to write a script that would basically import order information from an email and convert it, first in a new account (if the customer does not exist) and later create a Sale Order. So far, I have managed to do that, but the problem i find is when trying to convert the sale order into an invoice. Since this order comes from our webshop when we receive the email means it is paid, so my aim is that when creating the invoice from the Sale order, this would be marked as paid and set the amount due to zero.
This would sound a very easy task, but since our solution incorporates a payments module to manage the payment of an invoice, when i try to incorporate the payment entry within my script, there is when all the trouble starts. For some reason, it gets lost in its way when runnig the script and returns a partial payment all the time. The weirdest thing is thet if I run the script on debug mode, then all works perfectly, so my guess is that the issue may be related to the speed of the script.
So, is there any recomendation as for where to put a pause script step so the script will work also when run automatically?
I have tried every possible combination of long script, shorter with other scripts inside, perform script on server... and all the time something is wrong ;(
Thanks a lot for any insight thst would help us move forward, since we have been trying to solve this for a week already.
For an inventory management database, I'd like my main screen to be able to accept pulls from three related databases:
- Serialized (valuable tools, which I track and want back - the paintbrush);
- Replenishable (cheap tools that I buy by the yard and if one gets left behind I don't care - the paint-mix sticks);
- Perishable (disposable tools that are left on the job site - the paint).
These will handle their related requests differently. The serialized I'll be tracking properly to make sure we keep track; the latter two I'm looking for more like a system of 'tick marks' to help me know what we use on job sites.
We print our barcodes. For ease of use, I'd like staff to scan into a single field in an interface that is smart enough to do the right thing based on a key digit in the barcode. So when I scan barcode 'S1234', my db knows to move it to the Serialized relation field; when I scan 'P1234,' it knows we're in Perishables.
Looking for the elegant approach. My thought is that that central hot field (Scan_Here) will, when entered, store a variable and trigger a script built within the context of the related table, but I'm sometimes prone to reinventing wheels and doing stuff the long way, so I'm asking for suggestions / examples.
By JH Howland
I have created an "opener" file called "OpenMP" that is located on the Windows Desktop. Also, a global variable for the directory where the FMP14 files are located called "$$marinaDir" = "MarinaPro v17".
When activated the launcher opens but does not open the target file using the following file path, "filewin:/C:/$$marinaDir/Marina.fmp12." However if I substitute with the following, "filewin:/C:/MarinaPro v17/Marina.fmp12"; all is good.
The script elements follow:
Set Variable [$$marinaDir; Value: "MarinaPro v17"]
Open File ["Marina"] (Marina File Path: filewin:/C:/$$marinaDir/Marina.fmp12)
What am I missing?
I am having a tough time getting the set field by name script step to work and hoping someone can help me with this.
I have a file of sales transactions over many years. I have a related file for customers. The customer file has counters for how many times a customer visits each year, how many suits, sportcoats, etc. they buy each year ( visits_2017, visits_2016, visits_2015, suit_count_2017, suit_count_2016, suit_count_2015 and so forth). I would like my script to evaluate the year of the transaction in sales and update the appropriate counter in customers.
I have been unsuccessful in defining a variable and set field by name combination to accomplish this task. Any recommendations?
I'm reframing a question that I posted in a confusing way. Using variables seems so simple to me, but I know I'm missing something. I'll just post exactly what I'm trying to do so you guys can tell me why it isn't working.
The project is a db that will handle shift schedules for employees. In the one-day view I'm looking at, the essential live field is a global date field called gDate_of_work. A portal is looking through to related records and returning a list of employees (from a table called staff_schedule_match), identified here by unique serials, who are scheduled to work that day. There is a second portal, located on the same layout, that is (correctly) showing a separate related list, of employees who are available to work on the day of the week.
I, of course, want to be able to click on the name of an available employee and pass her serial number, along with the date in the global date field, to a new record in staff_schedule_match. In the distant past, I've sometimes solved this by opening layouts in offscreen windows and having extra fields dedicated to this data transaction, sometimes even by using the computer's clipboard (i.e. copy/paste).
The script I'm trying to execute here goes:
Set variable ($shift_add_nuid; employee's serial number from related record two) Set variable ($work_date; date displayed in this global date field) Freeze window Go to layout staff_schedule_match New Record Set Field (staff_schedule_match:nUID; $shift_add_nuid) Set Field (staff_schedule_match:StartDate; $work_date) Set Field (staff_schedule_match:EndDate; $work_date) Commit Record Go to layout (original) Refresh window Stepping through the script watching Data Viewer, I can see that the correct data is getting loaded into the variable values, but I can also see that the destination fields show up with an Unrelated table error. I don't understand why - I expected the behavior to be destination-agnostic, like my computer's clipboard, where if I copy some text in an email, I can paste it into a word processor or a browser or whatever.
Who Viewed the Topic