Archives
Here is a useful query to check user section that cause blocking / locking. SELECT d1.session_id, d3.[text], d1.login_time, d1.login_name, d2.wait_time, d2.blocking_session_id, d2.cpu_time, d1.memory_usage, d2.total_elapsed_time, d2.reads,d2.writes, d2.logical_reads, d2.sql_handle FROM sys.dm_exec_sessions d1 JOIN sys.dm_exec_requests d2 ON d1.session_id=d2.session_id CROSS APPLY sys.dm_exec_sql_text(d2.sql_handle) d3
In Syteline 9, there is one significant database schema change. All major tables like item are replaced with a view and _mst table. There are some context variables need to be set, before you can run query against to the views. Otherwise query to the view will return no data. And here is the variable […]
They are not stated in Syteline manual, but from my experience, I would suggest the following routine after upgrade a Syteline DB. 1) Regenerate _all table, by using “Update _All Tables” form. 2) Regenerate trigger, by using “Trigger management” form. 3) Regenerate Replication Triggers, if you are using multi-site replication. 4) Drop all the _tt […]
In the SyteLine database you will find Temporary tables that start with: tt_* tmp_* tmp_snapshot_* tmp_staging_* There are others that end with: _ii _dd _all. The first six are various forms of permanent "temporary" tables, used for temporary processing of data. The *_all tables are used to remove the requirement that another site must be […]
Below are some sample ways of constructing email body in Syteline event system. BODY( SUBSTITUTE(“We have a new customer. Please see customer number {0} for customer: {1}.”, FP(“custNum”), FP(“custName”) ) ) This uses the common SUBSTITUTE function and use object property as parameter value. BODY( IF( P(“POCost”) > 10000, GC(StdApprovalMessageBody), GC(StdRejectionMessageBody) ) ) Notice the […]
Under the BackgroundColor property, use this expression =IIF(RunningValue(Fields!grn_num.Value,countDistinct,Nothing) mod 2,"Silver","Transparent")
Table trigger is important part of Syteline data integrity. There are many validation logics safe guarded by trigger program. But in some circumstances, you may want to turn the trigger program off, in order load certain data. This is specially true during data conversion of your Syteline implementation, you may need to use program to […]
To extract the Event System metadata, please do the following: On the Syteline utility server, go to <install drive>:\program files\Infor\Syteline Double-click on AppMetadataTransport.exe On the first few forms of the wizard, enter the appropriate information (e.g., select to export the metadata to an XML file, pick the appropriate configuration, browse to enter an export file […]
Below are some sample ways of constructing email body in Syteline event system. BODY( SUBSTITUTE(“We have a new customer. Please see customer number {0} for customer: {1}.”, FP(“custNum”), FP(“custName”) ) ) BODY( IF( P(“POCost”) > 10000, GC(StdApprovalMessageBody), GC(StdRejectionMessageBody) ) ) BODY( FILECONTENTS(“X:\SL\Event\Message\Body\myPreparedMessage.txt”) ) BODY( FILECONTENTS(“X:\SL\Event\Message\Body\” + IDO() + EVENTNAME() “.txt”) ) BODY( DBFUNCTION( “MsgBodyFunction”, EVENTNAME(), […]