Use of RemoteID can differentiate users. But Tally listening to multiple ports - NO.
A Server even when listening to a single port should be able to process multiple clients using threads. If not so it is due to policy. Clients...
<ENVELOPE> <HEADER> <VERSION>1</VERSION> <TALLYREQUEST>EXPORT</TALLYREQUEST> <TYPE>Function</TYPE> <ID>$$CurrentCompany</ID> </HEADER> <BODY>...
if after one request the next request come before some interval of time Tally throttles. Or Is Tally using a different protocol,? Or will multi...
Posting vouchers individually you get feedback on each one of them. Combining them in one Xml you loose that but gain on network round trip...
Use Tally Server if justified. It is not throttled. Find what is new or modified. TDL functions like 'NumItems' come to mind. Collections (with...
LedGSTRegDetails collection works with newer version of Tally, old or new data
One way to reduce data to parse is to craft tdl for your purpose. Using collection approach is better one. Sometimes Report approach is the only...
To avoid collision use RemoteID. Each data source should post with its own Remoteid. This was found through testing for 'Merge Duplicate Ledger'...
In Internet Utf8 is the standard compatible with earlier Utf7 (English).
The application you used should be Unicode aware. In Unicode Code point, a number represents the actual character. In written form there are...
Yes Collections can hold multiple objects. So preferable.
General tips: 1. Incremental Exports like Daybook for each day. 2. Requesting only needed data / Fields. 3. Collections of narrower scope is...
Looks like working in Prime 3 too. ParyGSTIN works as long as it is within Collection
Xml is nothing but tdl wrapped in Xml. Download Tally Developer and browse source code. Please note that when you use Xml you should use it in...
Separate names with a comma.
