I agree with Rob. Application Server (AS) has a specific interface for scheduling TI. You can query the AS queue to trace how your TI workload is doing. We built a setup around this so our HR staff could post payroll journal files to SL, since we use a no-SL payroll system. The approach is something like: Licensing of the AS module. Setup the AS user and working environment. We have a virtual Windows 7 machine somewhere that's running the AS. Setup a web page with a file drope zone so the user can drag & drop the file. For some reason, we named our AS as "Atomic Ant", and even got a clipart for it, so the web portal is presented as that. This page triggers the automation ASDevObj.ASRequest object that is badly documented in the AS manual. Setup a second web page with pending and ready TI requests, based on a query over SYS.AppSrvRequest. A third page shows the detail of a specific job. This one is beyond the scope, since does a lot of log file parsing so it can highlite the offending data. As for stability, the main problem is to keep the AS instance running all the time. TI jobs has stronger requirements OS-wise, since it needs an open Window station. We use a third party monitoring system to aid on this.
↧
Forum Post: RE: Transaction import automation
↧
Forum Post: 2015 SL CU2 -- Can't install the SDK
I've just installed Dynamics SL 2015 CU2. On that server machine I have installed both Visual Studio 2008 and Visual Studio 2012 with Service Pack 5. I have opened and used both versions of Visual Studio on that machine. I tried installing the SDK from the CU2 distribution, but it went almost all the way to the end, and then gave the following Message: There is a problem with this Windows Installer package. A program run as part of the setup did not finish as expected. Contact you support personnel or package vendor. So I tried installing the SDK from the original installation package, rather than the CU2 package, but got the same error. I don't know what else to try. We previously had Dynamics SL 7.0 on this machine. Any suggestions or insight would be appreciated. Thanks!
↧
↧
Forum Post: SL 2015 -- Newly installed client won't open
I've just installed Dynamics SL 2015 CU2 on the server machine, and then ran ClientSetup to install the client on my local machine. The installation went through without incident, but when I start up the client I get the following error message, after which it exits: The client components on this machine are not up-to-date. This situation can result when a Service Pack is installed on the server but not the client. Please apply updates to this client computer. The installation program was from the latest updated version (CU2) on the server. Any help would be appreciated. Thanks!
↧
Forum Post: RE: SL 2015 -- Newly installed client won't open
Did you apply CU2 to the workstation? The ClientSetup.exe on the server doesn't get updated by CU2, so you have to run it at the workstations as well. It should only see the client to be upgraded.
↧
Forum Post: RE: Commission By Sales Person report is tripling results in SL 2015
I'm experiencing this problem in SL 2015 CU2. Was there a fix?
↧
↧
Forum Post: Payroll check deduction duplicating
Running live payroll checks. The detail that prints on the face of the check is duplicating every line. The totals all add up correctly. I've pulled queries from PRCheckTran and nothing is duplicated there. Looked at the check preview report and no duplication. Just the front of the check. My first assumption is that there is a form issue; but our IT manager who manages those state that it is the same form that our other entity uses where no problems exist. And no form changes have occurred recently; and this is a new problem. Anyone run into this issue previously? Thanks,
↧
Forum Post: RE: Add new calculated field in grid
Hi Nam, thanks for the answer, I ended in creating a temporary table to link all my calculated fields on. Look like it work now, I'll move everything in production today, will be the real test ;)
↧
Forum Post: RE: Payroll check deduction duplicating
When you see something like this it is typically caused by a duplicate record in a supporting table that is joined to the main record of the report. In this case, PRCHECKTRAN joins with the Deduction table and with the CalcChk table so I would examine both the CalcChk table and the Deduction table for duplicates. Please be aware that the Deduction table has entries for each calendar year. So, when looking for duplicates, you must look at the Dedid field and the CalYr field. However, it is not likely that the Deduction table is your problem because of the unique key structure on that table so I would focus on the CalcChk table. Note: this table should be empty after checks are kept (similar to PRCheckTran).
↧
Forum Post: RE: Payroll check deduction duplicating
Thanks for the response; checked both tables; including the CalcChk detail table just in case and didn't see any duplication. Please see the screen shot of the check for reference; maybe it includes a detail I'm not describing.
↧
↧
Forum Post: RE: Payroll check deduction duplicating
That section of the check joins PRCheckTran, CalcChk and Deduction so the duplication has to be in one of those 3 tables and, yet, you have indicated that PRCheckTran does not have duplicates and now you are saying the other two tables do not either. We are missing something here. Try running the following query and see if duplicates show: select * from prchecktran inner join deduction on deduction.dedid=prchecktran.dedid inner join calcchk on calcchk.empid=prchecktran.empid and calchk.chkseq=prchecktran.chkseq If this does not show duplicates then we know the database is fine and that the issue is, somehow, with the report definition. Which is refuted based on you statement that other entity uses the same report (unless, of course, the other entity is not on the same system). The only other tables that are involved are Country and Currncy tables (other than Employee and Batch) but those tables are not joined with PRCheckTran. One additional question: is this happening with all employees in all payrolls? And, what check format are you selecting? (OK, two questions).
↧
Forum Post: RE: Payroll check deduction duplicating
Ah you are correct, there is duplication when I do that. I was looking at the tables individually and not how they were linked. When I joined them the way you stated it did show up. What is the best method to remove the duplication?
↧
Forum Post: RE: Payroll check deduction duplicating
First you need to determine which table is causing the duplicates. The query I suggested shows all the fields from all 3 tables. So, look at a duplicate two lines and find which table has different values between the two lines. For example, if the deduction table is the culprit then the fields for prchecktran and calcchk will be the same on both lines but one or more fields in the deduction table will be different. Once you determine the table and the field(s) that are different then we can create a delete query to delete one of the two lines. This must be done with care so that it does not delete both lines so that is why we need to determine a field that is different.
↧
Forum Post: RE: Payroll check deduction duplicating
All fields between the two duplicated lines match...let me know if I messed up the joins: WHERE CalcChk.ChkSeq = PRCheckTran.ChkSeq AND CalcChk.EmpID = PRCheckTran.EmpId AND PRCheckTran.Col2Id = Deduction.DedId
↧
↧
Forum Post: RE: Payroll check deduction duplicating
Your join looks correct (my initial query had the wrong field name in prtran for joining to deduction so good catch there). There has to be at least one field that is different in order for this query to duplicate records or something is wrong with the indexes on one of the tables involved (not likely but cannot rule that out). We could use spHelp on each of the tables and look at the defined indexes on the table to see if they are correct but I would like you to look again for a different field content. To help some, you could add some additional where conditions to select only one resident ID and one deduction ID so you have just those records in you results. You know, I am looking at the data source and links for the report and I just realized that the prchecktran table joins the deduction table by using the Col2Id field only but the deduction table has rows for each calendar year so now I am wondering why there would not be an issue when you have had payroll active for more than one calendar year. It seems like that join would find records for more than 1 calendar year. I then looked at the filter in the report and that adds where deduction.calyr=the calendar year of the check so that means, in order to emulate the report you would have to add to your where clause deduction.calyr=2017.
↧
Forum Post: RE: Payroll check deduction duplicating
We only started using SL in 2017; so there shouldn't be prior year records in there yet. Yea, I was trying to wrap my brain around why there would be two rows with identical information...but I ran a formula to see if they matched in case I was overlooking a difference and they are identical.
↧
Forum Post: RE: Payroll check deduction duplicating
Sorry, ignore that; you are right. It wasn't active then but there were 2016 rows in the deduction table....I added that criteria and the duplication disappeared.... So I'm thinking it has to be the form? Thanks for all the support on this!
↧
Forum Post: RE: Payroll check deduction duplicating
So, if the query is not showing duplicates then I agree the next focus is on the report definition. Perhaps the filter in the definition is not checking the calyr field in the deduction table. If you have Crystal reports loaded you could pull up the 02.630 report (assuming you are using laser check by employee ID format) and look at the filter definition for that report. You can also look at the table joins using database expert and the link tab. You did not provide further detail on whether the working entity was using the same check format, was on the same system and was in the same database or not. We may need to alter our approach based on that information.
↧
↧
Forum Post: RE: SL 2015 -- Newly installed client won't open
Hi Stuart, Thanks for the info. I hadn't run the CU2 update on the local machine. Now that I've run it, however, I can't find the executable. I ran the SL2015_CU2.exe file and it said it was updating the client, and it continued on through completion, and everything seemed happy. When I look for the executable, however, I can't find it anywhere. Any suggestions? Thanks, Dan
↧
Forum Post: RE: Payroll check deduction duplicating
Same format, but this company is in a different database. Following is the selection; looks to include calyear from the deduction table: {Employee.CurrCheckCalc} <> 0 and {Employee.CurrNet} >=0 and Uppercase({Employee.Status}) = 'A' and {@MaskMode} = False and {Batch.Module} = 'PR' and Uppercase({PRCheckTran.Col1Type}) <> 'D' and ({Deduction.CalYr} = {@CalYr} OR {PRCheckTran.Col2Id} = '') and {PRCheckTran.ASID} = 0
↧
Forum Post: RE: Payroll check deduction duplicating
Also....the other companies without a problem are on their own database. This company has multi-site turned on with some other smaller entities. Those other shared companies are not using payroll. In the multi site, is there an exclusion needed on the site...not sure if any of these tables are shared.
↧