Thanks for getting back to me. Yes, youāre absolutely right. Weāre using Filemaker Pro as our main data source and have written an Applescript that can make the template for each product which we can then save for re-use later adjusting price/quantity etc by Applescript when required. Iāve noticed that in the last days eBay have started rejecting listings that donāt have the MPN attribute. If on creation of a template this attribute to default to "Does Not Applyā that would be a help but ideally weād be able to it programmatically so all our older templates could be adjusted. Obviously it would be better if we could actually input the correct MPN but the main thing is to stop the listings getting rejected.
Here something I built to let you insert item specifics through AppleScript. The syntax is somewhat ugly, because the way GarageSale stores item specifics maps very badly to AppleScript. It looks like this:
tell application "GarageSale"
setSpecific of first selected template with name "MPN" to value "123-456"
end tell
Or better yet: āgetSpecific of first selected templateā to get a list of all Attribute ānamesā and āvaluesā like:
Brand: Atlas
Type: Diesel Locomotive
MPN: 123456789012
I just looked up GarageSaleās scripting dictionary in the Script editor, and āconditionā and ābarcodeā are already there in the ātemplateā class.
Just like to say thank you as well for adding the SETSPECIFIC command - absolutely wonderful and something Iāve wanted to see for a long time.
I also second Nealās request if additional applescript commands could be added for attributes, such as a GETSPECIFIC - that way the existence and value of attributes can be checked allowing changes to be made dependent on the existing value or existence of a particular attribute.
The SETSPECIFIC is great but difficult to use in bulk as it automatically adds the attribute if it doesnāt already exist, something which is not always desirable.
In GarageSale 6.9.8, could you PLEASE add the corresponding getSpecific AppleScript command:
So I can find all āold/outdatedā Attributes:Custom Details fields in all my 11,000+ templates and remove or change them.
This will Greatly help in the cleanup of my MANY 11,000+ old templates before converting to the new GarageSale 7.
to get a list of all Attribute ānamesā and āvaluesā like:
Brand: Atlas
Type: Diesel Locomotive
MPN: 123456789012
tell application āGarageSaleā
getSpecific of first selected template
end tell
Or at least to get one named attribute:
123456789012
tell application āGarageSaleā
getSpecific of first selected template with name āMPNā
end tell
āAs mikeytttt also said:ā
I also second Nealās request if additional applescript commands could be added for attributes, such as a GETSPECIFIC - that way the existence and value of attributes can be checked allowing changes to be made dependent on the existing value or existence of a particular attribute.
The SETSPECIFIC is great but difficult to use in bulk as it automatically adds the attribute if it doesnāt already exist, something which is not always desirable.
Iāve been trying to extend the use of the setSpecific command and it is working wonderfully. One query though, where an item specific is a multi-select is ot possible to use this command to enter more than 1 value?
Iāve been trying various different syntax versions but havenāt found one yet.
An example might be for the ItemSpecific āAdditional Inputs/Outputsā.
I have tried
setSpecific of first selected template with name āAdditional Inputs/Outputsā to value "Analog In"
setSpecific of first selected template with name āAdditional Inputs/Outputsā to value "Analog Out"
setSpecific of first selected template with name āAdditional Inputs/Outputsā to value āMIDI I/Oā
but it just overwrites each time. Any bright ideas?
Itās a good thought and yes I have tried it but sadly it just adds a single line with the value Analog In, Analog Out, MIDI I/O rather than 3 different lines.
I also tried separating the values with a carriage return and a semi-colon but no luck.
However, if you need separate lines it might be needed to use slightly different names, like this:
setSpecific of first selected template with name āAdditional Inputs/Outputsā to value āAnalog Inā
setSpecific of first selected template with name āAdditional Inputs/Outputs #2ā to value āAnalog Outā
setSpecific of first selected template with name āAdditional Inputs/Outputs #3ā to value āMIDI I/Oā
Should be fixed here: