
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎12-21-2015 10:22 PM - last edited on ‎04-01-2024 04:38 PM by Mercedes_O
Any direction greatly appreciated.
1) In the "Configuration" "Asset Pages" "Asset Custom Fields" I set Custom01 to a Textbox and renamed it to TeamViewerID.
2) I created a batch file c:\tvr.bat with the following one line:
"C:\Program Files (x86)\TeamViewer\Version7\teamviewer.exe" --Password TestPassword -i {Custom01}
3) I then created an Asset Action called "TeamViewer Remote" that has one line:
cmd.exe /K {actionpath}tvr.bat
When I run the custom action from the Asset Pages everything translates okay except for the Custom01. Instead of it putting in the number that I manual put in by editing the asset it just puts in {Custom01} in the command line.
Question:
How do I call an "Asset Custom Field" from a command line or lansweeper action script?
- Labels:
-
API & Integrations

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-04-2019 11:29 PM
If everything is on the same network, you could use {ipaddress} to connect to the machines. You would have to modify teamviewer to accept incoming lan connection, but that should work.
Your batchfile should be:
"C:\Program Files (x86)\TeamViewer\Version7\teamviewer.exe" -p TestPassword -i {ipaddress}

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎10-10-2018 12:32 AM

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-09-2016 01:21 PM
{actionpath} - Network share path defined unter Configuration\Asset Pages
{smartname} - Assetname or IP address, depending on Asset type
{assetname} - Assetname
{dnsname} - Name as resolved by DNS
{computer} - Computer name
{domain} - Computer domain name
{tag} - Serial number
{username} - Logged on user name
{userdomain} - Logged on user domain
{ipaddress} - Asset IP address
{fqdn} - Asset FQDN
{scanserver} - Scan server which last scanned the asset

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎12-23-2015 05:33 PM
{actionpath}, {smartname}, {assetname}, {dnsname},
{computer}, {domain}, {tag}, {username},
{userdomain}, {ipaddress}, {fqdn}, {scanserver}, {assetid}
remark: {tag} is the serial of the asset

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎12-23-2015 05:04 PM
Thanks again.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎12-23-2015 04:43 PM
I'm afraid it's currently not possible to use the custom fields (eg. {Custom01}) as a parameter in custom actions.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-31-2016 03:42 PM
Bert.D wrote:
Hi,
I'm afraid it's currently not possible to use the custom fields (eg. {Custom01}) as a parameter in custom actions.
Hi,
is there any update?
It would be nice if the custom-fields could be used as a parameter in custom actions.
Maybe there is a 'workaround'?

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎09-27-2016 01:39 PM
MrCount wrote:Bert.D wrote:
Hi,
I'm afraid it's currently not possible to use the custom fields (eg. {Custom01}) as a parameter in custom actions.
Hi,
is there any update?
It would be nice if the custom-fields could be used as a parameter in custom actions.
Maybe there is a 'workaround'?
Unfortunately, there is no workaround available. The parameters you are able to use are hard-coded. The ability to use more parameters is on the wishlist but we cannot yet provide an estimated release date for this.
