Search Results for 'script'

[Sam Moffatt]

When you’re working with a linked record, you need to get a copy of that record. If you double click on “Procedures” it should insert some code to help you get the procedure record. It should look something like this (if it inserts just an ID then you can update it to match):

var procedures = record.getFieldValue('fld-1234');

Where the fld-1234 piece will be the value that the script editor puts in when you double click on the “Procedures” section heading. I did a video on building a script that has some details that might be useful. There are a few other videos on the channel that could fill in some gaps. There is also T.L. Ford’s Tap Forms Scripting 101 and 102 as other resources that might help.

That said since you’re on the “one” side of the 1:M field, if all you’re after is copying the value from the parent then using a calculation field is likely going to be simpler. Calculation fields in that situation will let you just double click the field you want and it should do the heavy lifting for you.

One schema recommendation is to use a third form that stores two link fields for going back to patient and procedure. You link 1:M from Patients and Procedures into this new form, let’s call it “Appointments” (I’d use “Operations” but that could be confusing), make sure you tick “show inverse relationship”. This leaves the “Appointments” with a single link back to the other two forms which means you can keep stuff like patient name unique unless you don’t have a lot of recurring patients. If what you’ve got it working that’s great but I’d generally take a step further to split patient from the instances of a procedure they have so that their data (name mostly it seems) is only in one place.

[Philip Jones]

Hello all,

I am trying to migrate an existing FM database to Tap Forms. Before I purchase I am trying to ensure I can make the basics of my existing db work.

Please forgive my naïveté as I am a beginning user of Tap Forms.

I have two tables: Patients and Procedures (surgical).

A patient can have one surgery; many people can have a given surgery. Therefore, on the Procedures table (screenshot 1) I have ‘Patients’ set up as a one:many field. I have the ‘link to form’ turned on so that, in my Patients table (screenshot 2) I can see the linked information correctly.

What I am attempting to do is to get the values of some of the related fields (from the Procedures table) into the Patients table. I am using a Script field for this. As per the attached screenshot, I am first trying to get the ‘OHIP code’ (‘C111A’ in the second screenshot) into its own field on the Patients table.

I have attached a screenshot of my script where I attempt to do so. It is not working and I know the fix is likely something quite simple.

In the Script window, the field ID was obtained by double-clicking on the “Code” field in the “Procedures” table on the left-hand side of the window.

Any help to get me on my way would be much appreciated.

Thank you.

Phil

Attachments:

You must be logged in to view attached files.

[Brendan]

Hi Chris,

That’s a cool use for Tap Forms!

I took astronomy in university. It was one of my favourite courses.

Although you’ve figured out another way to do what you want, your original question could be answered with a script to fetch an image from somewhere and populate the image in your form. If you had a folder on disk with photos in it, you could write a script to add a photo to your field from a URL using record.addPhotoFromUrlToField(url, field_id); You could set the photo field empty before adding a photo to it, otherwise you’d get multiple photos in the field.

Anyway, just thought I’d chime in with this bit.

Thanks!

Brendan

[Brendan]

What about something that triggers a Form Script in Tap Forms that uses the new parameters feature that then causes the script to call back to an Amazon API to get the product details? I don’t know anything about building Chrome extensions though.

But there’s information about calling a Tap Forms Script from a URL and passing it parameters here:

https://www.tapforms.com/help-mac/5.3/en/topic/javascript-api

[Brendan]

Possibly one way that would be relatively quick, although as Sam said, would get slower over time too, but would be easy to implement, would be a script that simply looped through all the records and re-numbered them all from 0…N, for whatever numbering scheme you are using. You wouldn’t need to look for holes as this would effectively eliminate holes and your new records would just go to the end. But then as Sam suggested, reusing IDs or in this technique, changing IDs of an item isn’t always a good idea. But it really depends on what your workflow is.

[Sam Moffatt]

I think a script would be a lot of overhead for this just because as the number of records increases, you’d have to scan through them to find where the holes are and allocate a new ID. It’s possibly but it’d get slower over time.

What I think might make more sense is a script you call to empty the record out and then a script field (that you can hide) that detects if some key fields are empty which you then key into a saved search for “available” records. Then you can repurpose those records as you need them.

I personally don’t think I’d ever want to reuse ID’s in a collection and would probably always keep them as is with a flag that says I don’t have the item any more but that’s perhaps just me.

[Sam Moffatt]

You can do it but it relies upon using CouchDB sync (or Cloudant) to land the items. I use CouchDB as my sync and I have a bunch of Greasemonkey/Tampermonkey scripts that I use to push stuff into Tap Forms.

Basically you can create a document in CouchDB with the same structure as a Tap Forms record. CouchDB let’s you do a POST to it to create a record via it’s web interface, Tap Forms then sees that record as a new record and it pops into it’s UI.

I have two scripts that I use to automatically import this forum into a Tap Forms document as I navigate around it, essentially each time I go to a page on the forum, it scrapes the page into CouchDB and then shows up in Tap Forms. Here’s a copy of the topic collector piece that shows importing topics and authors as new records. It’s a bit of a hack as there are some protections on the tapforms.com side to prevent sending to external domains (hence the cspbypass.google-analytics.com hack).

I started building one to import Amazon product pages but I never finished it. It’s a fair amount of work to basically use Javascript to extract out the pieces of the page you’re interested in and then splice it into a Tap Forms document. Not impossible just time consuming.

[Eric de Mildt]

Hi Sam,

Thanks for your reply and pointing this out!
Field script does the trick, rounds up from 0,5.
So it works!
I’m anything but a programmer, didn’t know about these rounding rules (Rounding is no a straightforward subject though once you start reading on the subject ;-) But interesting ).

Cheers
Eric

[Nils B]

First of all, I know about the auto-increment function of a number field. But it’s not what I am looking for. Why? Because the field continues to count from the last position even if old records are deleted.

This means:

I need a script to fill in the gaps (freed up inventory slots) in the database when records are deleted and after that, created.
I want to use the inventory number as just it, a fixed number for a record (readable) and I don’t want gaps.

Can somebody help me with it? I think it’s understandable that you need something like this for managing collections of items (i am a collector).

Thanks!

[Sam Moffatt]

Nice start to a generic entry point! I have some suggestions for improvements :)

Instead of this long line:

if (param == 'JLRouteScheme' || param == 'JLRouteURL' || param == 'formID' || param == 'JLRoutePattern' || param == 'docID' || param == 'scriptName')

You could use an array and simplify the if statement and skip to your else directly by using Array.includes:

var ignoredParams = ['JLRouteScheme', 'JLRouteURL', 'formID', 'JLRoutePattern', 'docID', 'scriptName'];
if (!ignoredParams.includes(param)) {

The other thing would be to use a switch statement instead of the if/else:

			var theField = form.getFieldNamed(param);
			if (theField == undefined) {
				console.log(`No field called ${param}`);
				continue;
			}
			switch(theField.fieldType) {
				case 'text':
				case 'web_site':
					record.setFieldValue(theField.getId(), parameters[param]);
					break;
				case 'photo':
					record.addPhotoFromUrlToField(parameters[param], theField.getId());
					break;
				case 'script':
					console.log('Cannot set value for a "script" field type');
					break;
				default:
					console.log(`Unsupported field type ${theField.fieldType}`);
			}

[Sam Moffatt]

I’ve not personally noticed the rounding behaviour but it sounds to me like an implementation of IEEE 754’s rounding rules for round half to even which is a strategy for mitigating rounding bias.

You might be able to use a script field to have Javascript do the rounding for you, I believe it uses the round up strategy.

[Eric de Mildt]

Am I right in finding that 0.5 is occasionally rounded down instead of up? Is it that rounding decimal places in Javascript can go “quirky”? And can it be solved in TF calculation fields?
What would be the best approach?
Thanks for any advise.

Eric

[Martin Kendall]

Hi,

I just made a quick utility to simplify adding records to Tap Forms from other apps.

It actually allows adding of records from any app (e.g. Shortcuts, Drafts) that can call a URL.

To use:
1) Install: Add the attached script as a form script to the form you want to be able to add records to.
2) Run the script in Tap Forms and it will display the URL you need to use in Shortcuts to add a record
3) Create a Shortcut calling that URL with the parameters matching the field names in the form (for the fields you want to set)

I’ve only added support for adding text values, URLs and photos, but there is nothing to stop other field types, such as rating, being added.

Hope someone finds this useful,

Martin

Attachments:

You must be logged in to view attached files.

[Brendan]

Hi Chris,

You’re right. It’s not working right for checkmark field types. I’m working on fixing that. In fact, I just fixed it (for the next update).

In the meantime, you can write a Form Script to accomplish the same thing that loops through the records, looking for the checkmark field value and turning it off if it’s on.

Are you familiar with scripts in Tap Forms yet? Here’s a sample bit of code that will do that for you, but you’d have to put your own Checkmark field’s ID in it:

function Toggle_Checkmark() {
   var records = form.getRecords();
   var check_mark_id = 'fld-f14ccd51913b4348b2c32d9ac4eaf7f2';

   for (var index = 0, count = records.length; index < count; index++){
	// do something;
	var record = records[index];
	var value = record.getFieldValue(check_mark_id);
	if (value == true) {
		record.setFieldValue(check_mark_id, 0);
	}
   }
   form.saveAllChanges();
}

Toggle_Checkmark();

Thanks,

Brendan

[Sam Moffatt]

If you were to aim to optimise the script, I’d probably want to have a map of PDF name to Tap Forms record ID. You can do a retrieve of a record by key/record ID via the script so if you precomputed a map of these keys or used the record ID import mode for Tap Forms to import the records then it’ll be a single retrieve for retrieving the record (form_record_id is the field in the CSV file which if present will be prepended with a rec- prefix and allow you to use form.getRecordWithId). The horse has likely already bolted for this one but something to consider for future projects, so let’s go ahead with the other suggestion: PDF attachment name in a script field.

If you have the PDF attachment name in a script field, you could use the getRecordFromFormWithKey function in my script manager. The method signature looks like this:

getRecordFromFormWithKey(formName, keyFieldId, keyValue, createIfMissing = true, earlyTermination = true, alwaysScanOnMiss = false)

It creates in Javascript an index on a first pass and then does looks up from there (set earlyTermination to false and alwaysScanOnMiss to true). When you’re in a tight loop this should improve performance by doing the record loop once to build the index and then you can do a similar sort of roughly constant time retrieval for matching records. It’s still two loops but you remove the nesting and replace it with a more optimised data structure.

First step is to create a new script field in your Contracts form and in it you want to add in the code we use to grab the filename from the PDF:

record.getFieldValue('fld-e870153bd0a647c9823ca998c213d1fd')[0].filename;

You’ll need to tick the “Update records when saving” option when creating that to populate the new field in all of your record. Essentially we’re just copying the filename as a new field. At this point you might also want to setup a search to look for records that have this field empty because that seems likely a bug. You’ll also need the field ID from the form panel (underneath the “Description” field) which I refer to later as “fld-scriptfieldidhere” that you’ll need to change.

Using the code you provided as a basis, something like this should get you some of the way there:

document.getFormNamed('Script Manager').runScriptNamed('getRecordFromFormWithKey');

function Update_Records() {

    var csvForm = document.getFormNamed("csv");

    // Contracts
    var keyword_id = 'fld-a2126cbe512646e9ba144fb5a90b06dc';
    var pdf_id = 'fld-3ea77ccc18604174b722ece105965c44';

    // get use fixed field Id
    var csvPdf_id = 'fld-4bcd0f1fba5c4178bb8d10a112b17489';
    var csvKeyword_id = cvsForm.getFieldNamed('Keyword').getId();

    // Loop over all csv entries
    for (entry of csvForm.getRecords()) {
        // get pdf file name of CSV record
        var csvPdfName = entry.getFieldValue(csvPdf_id);

        // replace spaces with underscores
        csvPdfName = csvPdfName.replace('/ /g', '_');
        console.log("Processing: " + csvPdfName);

        contract = getRecordFromFormWithKey("Contracts", "fld-scriptfieldidhere", csvPdfName, false, false, true);

        if (!contract) {
            console.log('Unable to find matching PDF record: ' + csvPdfName);
            continue;
        }

        console.log("Found match: " + csvPdfName);

        // Update contract record
        var type_of_agreement_id = 'fld-6af499ed439143b297828643341d939b'
        contract.setFieldValue(type_of_agreement, 'Licensing Agreement')

        // This should “replace” keyword or keywords in a selected record
        var agreement_keywords_id = 'fld-a2126cbe512646e9ba144fb5a90b06dc';
        contract.setFieldValue(agreement_keywords_id, entry.getFieldValue(csvKeyword_id));
    }
    document.saveAllChanges();

    return 'done';
}

Update_Records();

We’ve still got the outer loop that iterates over the incoming CSV form, the “Contracts” loop is removed and replaced with the call to getRecordsFromFormWithKey which internally does a loop for you but also builds an index in memory that should make subsequent accesses quicker. Watch your memory usage in Activity Monitor but you’ve got 64GB of RAM so we should be fine. The script is finding the record for you so the code that lived inside your inner for loop moves up a level though there is a check to see if we got a record back. I did some minor changes to set the keyword based on the CSV form as an example of how I think that to work.

One thing I’ve done in scripts like this is put in a field for when it was processed to be able to skip it and also a counter to limit how many records are processed. This is useful for debugging scripts and being able to progressively execute it to get an idea of it:

let minTime = new Date().getTime() - 86400000; // one day
let processed = 0;
let skipped = 0;

for (...) {

    let previousDate = entry.getFieldValue('fld-previousdateidhere');
    if (previousDate && previousDate.getTime() > minTime) {
        skipped++;
        continue;
    }

    entry.setFieldValue('fld-previousdateidhere', new Date());

    processed++;

    if (processed > 100) {
        break;
    }

    // your existing for loop logic here
}

This uses an extra field and updates when the script is run to set it that way the next time you run the script, it skips past records it’s already “processed” so to speak and moves onto the next batch of 100. Instead of handling the date logic in code, you could also tie this into a saved search as well so that Tap Forms only gives you the candidate records.