Skip to content

Commit

Permalink
code fix on GetNewNumber issue (#8)
Browse files Browse the repository at this point in the history
  • Loading branch information
koechlm committed Sep 3, 2020
1 parent fc623b6 commit 6c5dd4c
Show file tree
Hide file tree
Showing 3 changed files with 4 additions and 8 deletions.
1 change: 1 addition & 0 deletions .gitignore
Original file line number Diff line number Diff line change
Expand Up @@ -34,3 +34,4 @@
/iLogic-Vault-QuickstartLibrary/QuickstartiLogicLibrary2020.25.2.1.zip
/iLogic-VaultInvServer Library/obj/x64/Release
/iLogic-VaultInvServer Library/bin/x64/Release
/iLogic-VaultInvServer Library/obj/x64/Debug
4 changes: 2 additions & 2 deletions iLogic-Vault-QuickstartLibrary/Properties/AssemblyInfo.cs
Original file line number Diff line number Diff line change
Expand Up @@ -32,5 +32,5 @@
// You can specify all the values or you can default the Build and Revision Numbers
// by using the '*' as shown below:
// [assembly: AssemblyVersion("1.0.*")]
[assembly: AssemblyVersion("2021.26.0.0")]
[assembly: AssemblyFileVersion("2021.26.0.0")]
[assembly: AssemblyVersion("2021.26.0.1")]
[assembly: AssemblyFileVersion("2021.26.0.1")]
Original file line number Diff line number Diff line change
Expand Up @@ -696,11 +696,6 @@ public IList<string> CheckFilesExistBySearchCriteria(Dictionary<string, string>
public string GetNewNumber(string mSchmName, string[] mSchmPrms = null)
{
AWS.NumSchm NmngSchm = null;
if (mSchmPrms == null)
{
mSchmPrms = Array.Empty<string>();
}

try
{
if (mSchmName == "Default")
Expand All @@ -711,7 +706,7 @@ public string GetNewNumber(string mSchmName, string[] mSchmPrms = null)
{
NmngSchm = conn.WebServiceManager.NumberingService.GetNumberingSchemes("FILE", AWS.NumSchmType.Activated).First(n => n.Name == mSchmName);
}
return conn.WebServiceManager.DocumentService.GenerateFileNumber(NmngSchm.SchmID, null);
return conn.WebServiceManager.DocumentService.GenerateFileNumber(NmngSchm.SchmID, mSchmPrms);
}
catch (Exception)
{
Expand Down

0 comments on commit 6c5dd4c

Please sign in to comment.