I found the answer thanks to this post on tek-tips.com (www.tek-tips.com/viewthread.cfm). The golden nugget was the mention of a procedure creating it's own table buffer. I am in fact using a procedure. When I added the in parameter and passed the table from the form event handler it worked! Thanks again for your input!
↧
RE: range where isn't working
↧
range where isn't working
I'm trying to use a range where clause but I always get all rows back in the window. I've used SQL Profiler to see what's happening and I don't see the where clause being added. Here's what I'm doing:
range clear table TBLNAME;
range table TBLNAME where physicalname('field_name' of table TBLNAME) + " LIKE '%" + strVal + "%'";
fill window WINDOW_NAME;
The help file is pretty limited and I've found a lot of examples that use the above. What am I missing?
↧
↧
RE: GP2010 upgrade path?
Thanks Richard. Appreciate the feedback. Any thoughts on upgrading to GP2015 vs. GP2016? The latter is fairly recent and therefore unproven as yet, so I'm wondering if it makes more sense to go with GP2015 which I presume is a stable option.
↧
RE: GP2010 upgrade path?
Do you use the GP web client? If not, go straight to GP 2016. There is a minor issue with having multiple unrelated windows open with the GP 2016 we client.
↧
GP2010 upgrade path?
We have been running MS Dynamics GP2010 for the past 4+ years and our Accounting team is ready for an upgrade. I'm wondering if going straight to GP2016 is the best option. Can we go to straight to GP2016 or must we do incremental upgrades? Would GP2015 be a more stable option? Any suggestions, input, recommendations would be appreciated.
Thanks,
Wes
↧
↧
VBS File Used for the Scribe Job is Removing the Source File of the Scribe Job
Hello:
At the end of this posting are two VBS script files. The first is designed to move a file from one folder (the "OnDeck" folder) and place the file into another folder (the "Input" folder), as a renamed file.
The renamed file in the "Input" folder is, then, to be used as the source file for an application called Scribe that imports data from that source file into Microsoft Dynamics GP 2013 R2.
The second script, CopyFile.vbs, seems to work fine. It simply archives the source file in the "OnDeck" folder and places it into the "Archive" folder within "Input" as a Scribe "post job" step.
I believe that the issue lies with the first script--MoveAndRenameFile.vbs.
Here's the "issue" that I speak of. Prior to the running of the MoveAndRenameFile.vbs file, there is already a source file within the "Input" folder, from the previous time that the Scribe job ran. But, the problem is that this MoveAndRenameFile.vbs causes the source file in "Input" to disappear.
The source file is called "AP_Trans.txt".
The thrust of the MoveAndRenameFile.vbs file is to, again, simply move the file from the "OnDeck" folder and place it into the "Input" folder as a renamed source file for Scribe to process and import data from.
I have attached a screenshot from a Word document of the Scribe window that controls the "pre job" task and parameter and the "post job" task parameter. The issue, like I said, is with the "pre job" section
I have, also, attached a screenshot of Step 3 showing the "OnDeck" directory.
I know it seems odd to have the "OnDeck" directory in Step 3 and not Step 2, since Step 3 represents where Scribe pulls the source file from and the source file "Input" folder is shown in Step 2. But, a consultant tells me that Scribe runs Step 3, prior to Step 2--as odd as that sounds.
Any thoughts?
Thanks!
Much appreciated!
John
MoveAndRenameFile.vbs:
'****************************************************************************************
' MoveAndRenameFile.VBS
' This script takes three parameters that indicate where the
' Parameters:
' SourceFilePath (the original file, with the full path)
' TargetFolder (moves the file here)
' TargetFile (renames the file to this name)
'****************************************************************************************
Option Explicit
const APPLICATION_NAME = "MoveAndRenameFile"
Dim exitcode : exitcode = 0
Call Main()
WScript.Quit exitcode
Function Main()
Const ForReading = 1, ForWriting = 2, ForAppending = 8
Dim FSO, logFile
Dim sSourceFilePath, sSourceFile, sTargetFolder, sTargetFile, sTargetFilePath
Set FSO = CreateObject("Scripting.FileSystemObject")
Set logFile = FSO.OpenTextFile( "C:\Files.log", ForAppending, True )
logFile.Write vbCrLf
logFile.Write FormatDateTime( Now, 0 ) + vbCrLf
' Ensure that a valid target file has been specified
On Error Resume Next
sTargetFile = WScript.Arguments(2)
If (Err.Number <> 0) Then
' Call MsgBox("The following parameters must be specified:" & vbCrLf & _
' " SourceFilePath (the original file, with the full path)" & vbCrLf & _
' " TargetFolder (moves the file here)" & vbCrLf & _
' " TargetFile (renames the file to this name)", _
' vbOKOnly, APPLICATION_NAME)
exitcode = 901
Exit Function
End If
On Error GoTo 0
sSourceFilePath = WScript.Arguments(0)
sTargetFolder = WScript.Arguments(1)
logFile.Write "Source File: " + sSourceFilePath + vbCrLf
logFile.Write "Target Folder: " + sTargetFolder + vbCrLf
logFile.Write "Target File: " + sTargetFile + vbCrLf
' Validate the source file
If Not (FSO.FileExists(sSourceFilePath)) Then
' Call MsgBox(sSourceFilePath & " is not a valid source folder/file.", _
' vbOKOnly, APPLICATION_NAME)
exitcode = 901
Exit Function
End If
' Validate the target folder
If Not (FSO.FolderExists(sTargetFolder)) Then
' Call MsgBox(sTargetFolder & " is not a valid target folder.", _
' vbOKOnly, APPLICATION_NAME)
exitcode = 901
Exit Function
End If
sSourceFile = FSO.GetFileName(sSourceFilePath)
sTargetFilePath = sTargetFolder & "\" & sTargetFile
' Call MsgBox(sSourceFile & vbCrLf & sTargetFilePath, vbOKOnly, APPLICATION_NAME)
' Delete the target file if it's already there
If (FSO.FileExists(sTargetFilePath)) Then
FSO.DeleteFile(sTargetFilePath)
End If
' Move and rename the file
On Error Resume Next
FSO.MoveFile sSourceFilePath, sTargetFilePath
If (Err.Number <> 0) Then
exitcode = 901
End If
On Error GoTo 0
logFile.Close
End Function
CopyFile.vbs:
'****************************************************************************************
' MoveAndRenameFile.VBS
' This script takes three parameters that indicate where the
' Parameters:
' SourceFilePath (the original file, with the full path)
' TargetFolder (moves the file here)
' TargetFile (renames the file to this name)
'****************************************************************************************
Option Explicit
const APPLICATION_NAME = "MoveAndRenameFile"
Dim exitcode : exitcode = 0
Call Main()
WScript.Quit exitcode
Function Main()
Const ForReading = 1, ForWriting = 2, ForAppending = 8
Dim FSO, logFile
Dim sSourceFilePath, sSourceFile, sTargetFolder, sTargetFile, sTargetFilePath
Set FSO = CreateObject("Scripting.FileSystemObject")
Set logFile = FSO.OpenTextFile( "C:\Files.log", ForAppending, True )
logFile.Write vbCrLf
logFile.Write FormatDateTime( Now, 0 ) + vbCrLf
' Ensure that a valid target file has been specified
On Error Resume Next
sTargetFile = WScript.Arguments(2)
If (Err.Number <> 0) Then
' Call MsgBox("The following parameters must be specified:" & vbCrLf & _
' " SourceFilePath (the original file, with the full path)" & vbCrLf & _
' " TargetFolder (moves the file here)" & vbCrLf & _
' " TargetFile (renames the file to this name)", _
' vbOKOnly, APPLICATION_NAME)
exitcode = 901
Exit Function
End If
On Error GoTo 0
sSourceFilePath = WScript.Arguments(0)
sTargetFolder = WScript.Arguments(1)
logFile.Write "Source File: " + sSourceFilePath + vbCrLf
logFile.Write "Target Folder: " + sTargetFolder + vbCrLf
logFile.Write "Target File: " + sTargetFile + vbCrLf
' Validate the source file
If Not (FSO.FileExists(sSourceFilePath)) Then
' Call MsgBox(sSourceFilePath & " is not a valid source folder/file.", _
' vbOKOnly, APPLICATION_NAME)
exitcode = 901
Exit Function
End If
' Validate the target folder
If Not (FSO.FolderExists(sTargetFolder)) Then
' Call MsgBox(sTargetFolder & " is not a valid target folder.", _
' vbOKOnly, APPLICATION_NAME)
exitcode = 901
Exit Function
End If
sTargetFile = FSO.GetFileName(sTargetFile)
sTargetFilePath = sTargetFolder & "\" & sTargetFile
' Call MsgBox(sTargetFile & vbCrLf & sTargetFilePath, vbOKOnly, APPLICATION_NAME)
' Delete the target file if it's already there
If (FSO.FileExists(sTargetFilePath)) Then
FSO.DeleteFile(sTargetFilePath)
End If
' Move and rename the file
On Error Resume Next
FSO.CopyFile sSourceFilePath, sTargetFilePath
If (Err.Number <> 0) Then
exitcode = 901
End If
On Error GoTo 0
logFile.Close
End Function
↧
RE: Customer ID not Visible in look ups
If they click the looking glass and search by customer name instead of customer ID, can it be found that way or even just by scrolling through the window? That might be a temporary solution. Otherwise removing the space through SQL might be the next needed steps.
↧
Customer ID not Visible in look ups
Hello,
I have a client where the customer ID is not visible in GP lookup and she cannot type in the customer number to apply a cash receipt against the account.
Background: The customer account was passed to GP with the space and the sales order is posted and open in GP, however the cash receipts entry window cannot find the customer ID in the smart list look-up to apply the cash receipt and you cannot type the costumer ID in with a space in front of it. You can locate the posted sales order under the document number under Sales Inquiry.
Does anyone know how to resolve this lookup problem?
Thank you,
Donnette
↧
RE: MR DB Restore & report Export /Import for GP Environment
I'd suggest exporting out the reports from test and importing them in to the Production server. That's generally the easier route.
↧
↧
RE: MR DB Restore & report Export /Import for GP Environment
Hi Matt,
Thanks for the reply.
I tried to export the reports, i have sleeted all the reports in the report definition tab from the building block groups, but in Row definition tab some definitions were selected automatically and some were not selected.
may i know the reason for this?
And do i need to separately export the row definition that were not selected and need to import them again?
Regards,
Aravind Reddy.
↧
RE: MR DB Restore & report Export /Import for GP Environment
If they are associated (assigned) to report definition, they will be selected automatically. If you want to export everything, just hit Select All for each of the tabs. on the Export window and that will ensure that you get everything.
↧
GP2015: SQL Error with the Letter Writing Assistant
Hello,
I need some help fixing an issue we are having with the Letter Writing Assistant. We are using Dynamics GP 2015 and one of our HR staff recently encountered this issue when trying to prepare rejection letters for some recently interviewed applicants. These are the steps she follows:
1) She navigates to Reports > Letter Writing Assistant (and Next);
2) She clicks on Prepare the letters using an existing letter. (and Next);
3) She clicks on Applicant (and Next);
4) She selects Requisition Number from the dropdown list, enters the same requisition number in the From and To textboxes, and selects Rejected from the type of applicants to include (in fact, any type still produces the issue);
5) After clicking Next, she receives the error below:
SQL Error: 102 [Microsoft][SQL Server Native Client 11.0][SQL Server]Incorrect syntax near 'andDYNAMICS'.
6) When she clicks OK, another window opens where she chooses the Decline option:
7) After clicking Next, the "Applicants to receive a letter" window displays with an empty list.
I'm guessing the SQL query fails to return the list of applicants who have been rejected for the specific requisition number. Has anyone encountered this issue and successfully fixed it?
Note: She can generate the letters individually through the Employee card but it would be much easier to pull the listing and generate the letters as a group using the assistant.
Thanks.
↧
RE: Field Level Security - Hidden Field not hidden
Thank you David for the insight. I think the way forward will be to modify the window for that user. Are there any links or procedure manual to instruct one how this can be done for a single user? The other users will still need access to the full screen so I think this will have to be done carefully.
↧
↧
RE: Inventory-->Reports-->Serial/Lot--> Lot Number report.
Hi Sandip,
Have you tried checklink and reconcile inventory, this helped me on the same issue in the past.
↧
Inventory-->Reports-->Serial/Lot--> Lot Number report.
Hello,
Inventory-->Reports-->Serial/Lot--> Lot Number. In this report Quantity Available is 0 and report is still showing those Lots details. Not able to find out what is cause?
Any update on this will be highly appreciable.
Thanks much
Sandip Jadhav
↧
RE: Unable to open support ticket via customer source.
Hi Kirk,
Normally I will email them directly with customer source details and they come back pretty quick.
↧
Unable to open support ticket via customer source.
Has anyone else been having trouble opening technical support requests via customer source? I have been trying to open one since yesterday with no luck.
Thanks,
Kirk
↧
↧
RE: Issues printing
Hi,
Please check whether printer has original driver, also check whether setup of page landscape or portrait change it and try to print again.
↧
Issues printing
Hello All,
Our end-user is having issues with a report out of Dynamics, it prints, however it is cutting off information (right side).
Any help is appreciated.
Thanks much,
Ani
↧
How to insert an integration manager field into my script?.
Hi.
How can I insert a specific field in the integration manager for this code?.
Example:
Command.Parameters.Append(Command.CreateParameter("@PropertyValue", 200,1, 133, "HERE integration manager field"))
set connectionPuma = CreateObject("ADODB.Connection")
set command = CreateObject("ADODB.Command")
connectionPuma.ConnectionString = "Provider=SQLOLEDB.1;Password=123456;Persist Security Info=True;User ID=test;Initial Catalog=Development;Data Source=gemini"
connectionPuma.Open()
command.ActiveConnection = connectionPuma
command.CommandText = "sp_InsertarFacturaMagaya"
command.CommandType = 4
Command.Parameters.Append(Command.CreateParameter("@ObjectType", 200, 1,31, "SOP"))
Command.Parameters.Append(Command.CreateParameter("@ObjectID", 200, 1,61,SourceFileds("Type.invoice")))
Command.Parameters.Append(Command.CreateParameter("@PropertyName", 200,1, 31, "GUID"))
Command.Parameters.Append(Command.CreateParameter("@PropertyValue", 200,1, 133, "TESTING"))
command.Execute()
connectionPuma.Close
↧