llGiveMoney & Transaction History

Hi

I have several items that make payments to residents. However, when checking my transaction history to find out which items are paying, it only shows "Object Pays".

How can you set a payment description/object name to show in the transaction history? Surely it *must* be possible to do?

Any ideas?

Gomez

No way I know of.

Think of it this way, if it didn't tell you it was an object and you could set the description/name, wouldn't it be open for abuse?

Might be worth suggesting it as a feature that in addition to the "object payment" you can append with a string of x chars.

In the mean time, develop a means of recording the transactions yourself with LSL, e.g. email update giving all the details you require. Or perhaps a MySQL database which stores the info for you. You could store the details in a seperate script which just dumps them all to chat when you request it (limited though as far as script memory will allow).

Yes, I see your point, but there is already a description field that COULD be used with the object name that the instruction came from inserted automatically - that way it would still be an "object pays" entry, but you could also see from the description field which object it was.

I do already get it to IM me with the details, but it seems a messy way of doing it without using an external database. Would not "fixing" this also help with sim lag - then scripts would not need to send IM's/Emails or connecting to databases, if this was just a standard feature

I'm amazed with all the latest develolpments in SL that the Lindens are working on, such a basic but necessary thing is overlooked...

Gomez

A prims default name is "Object".

Do rename your prim to whatever you like and that should show up in the transaction log.

That doesn't apply to this issue Squirrel. Check your Linden Dollar Transaction History and you would see the following for an llGiveMoney call:



The value Type: is either Object Pays, Payment, Parcel Directory Fee, Gift, Give Inventory, Object Sale etc. and does not refer to an object by the name "Object". What Gomez is asking for is to have an additional field with From: which details the object's name or UUID (at least some defining aspect of the object).

in the meantime....

usually i can tell what it was by what region it was in. but if you have fifty objects in one region, that's no help, of course.

the other thing is, you can script the object to email you transaction details. all my vendors do this. the svn (simple vendor nexus) vendors have a very robust batch-emailing routine that keeps your main script from... what is it, sleeping 20 minutes while it sends email? :X

er, seconds, yeah, i meant seconds...

Yes, the email idea would have been a better solution than IM (i do redirect IM's to email when I'm offline, but then when I'm online I then have no perminant record), but the 20 second sleep time with llEmail cause other problems.

Gomez

What Bloodsong proposed was a secondary script dedicated to sending the e-mail. This would presumably take the data from a link_message and perhaps (if I understand his mention of batching) store several records until a sufficient amount of data has been collected before sending it all via llEmail to your account. This means fewer emails and no 20sec delay (for your main script). Sounds like a win-win situation to me.

Edit: if you don't like the thought of having the data sitting around waiting for a few more payments it could start a long delay (like an hour or so) and send off the email even if it didn't meet the quantity quota. That way you'd get confirmation of a sale within an hour max and still be able to reduce the number of emails if you had more than one sale through that vendor in an hour. (Obviously that sounds more attractive if you replace hour with day or even week depending on your requirements).

I set my vendor object description to something meaningful, this I will see in the transactions history, so no problem to see which item pays to which residents.


Regards Shyan

Yes this works perfectly. Example:

Without an item description:

Date: 2008-07-15 09:51:52
Object Pays
Region: Anywhere Camping Island
Source: AnywhereCamping Preiz

With a description:

Date: 2008-07-12 23:38:37
Payment
Description: DERANGED SPLODER
Region: The Central
Destination: Naughtybuttnice Munro

To reiterate, note that--just like for IMs and chat--it is the name of the PRIM THE SCRIPT IS IN, not the OBJECT (root prim) that shows up in your transaction history. So if a script in a child prim makes payments and you want something meaningful to show up, you must give that child prim itself a meaningful name. You can do this from a script in the child prim (llSetObjectName()), before linking, or by selecting "Edit linked parts" in the edit window, selecting only the prim in question, then changing the name in the "general" tab of the edit window.