[David david@winthropdc.com]

Up

0

Down

::

Hi Raul

Creating a Service Procedure for use with SBA requires Dexterity. The DLL component is created automatically via the DAG.exe tool.

The security is handled by a Windows Active Directory account for logging in which is tied to a SQL account. Access to the particular Service Procedure is handled by the application level security.

Another option for you is to use GP Power Tools. The Developer Tools module has the ability to create custom Service Procedures which can be called externally or from within GP (via Dexterity, VSTools or GPPT). GPPT can also create custom URL Drill Backs and custom Report Writer (RW) functions.

We also have our Batch Posting Service Toolkit tool which can post batches via Web Service or direct calls.

If you need to get into more specifics, let me know as they are some tricks you will need to know to get SBA working for your own Dexterity products.

Kind regards

David

[David david@winthropdc.com]

Up

0

Down

::

I would check with Integrity.

APR could be Advanced Pay Roll or something like that.

Also look at this Benefits Presentation

https://www.winthropdc.com/ftp/pub/GPPowerTools_Benefits.ppsx

You can easily fix your GP Power Tools deficiency.

Regards

David

[David david@winthropdc.com]

Up

0

Down

::

You have a customization installed which will also need to be updated for the Year End update.

The trigger that is failing starts with APR, look at your installed products in the Dynamics.set and identify which product is named or written by APR.

If you have GP Power Tools, you can use the Resource Information window in Procedure mode and enter the trigger script’s name and it will identify which product the script is from.

Once you know the product, please contact the developer for more information.

One other possibility is that there is an alternate version of that window that is not enabled and so the URL field is missing. Best coding practice should prevent an illegal address error if an alternate window is not opened by security, either aborting the code or displaying a warning to change security settings. But maybe the developer has not followed best practices.

Regards

David

[David david@winthropdc.com]

Up

0

Down

::

Hi Abdel

You are doing nothing wrong. Sadly, I have checked the source code and the original developer has not added a check for the required() function in the Scrolling window change script that does the saving.

So while you have correctly made the field required, there is nothing in the code to enforce the required fields.

You can use GP Power Tools Developer Tools to add a check for required fields and abort the save with the appropriate error message.

[Edit] I have passed the details of this bug back to Microsoft.

Kind regards

David

[David david@winthropdc.com]

Up

0

Down

::

You could set up sending emails with GP Power Tools running a query and returning the results via email.<div>

Or use the business alerts functionality.

Regards

David

</div>

[David david@winthropdc.com]

Up

0

Down

::

Yes Larry. <div>

But we could update the example to have another colour when the credit limit is 80% used.

Regards

David

</div>

[David david@winthropdc.com]

Up

1

Down

::

Hi Larry

We could look at updating the free GPPT Form Control sample that adds a customer status to every window where customer number is shown to have a warning at 80%

https://winthropdc.wordpress.com/2024/10/13/gppt-form-control-adding-a-customer-status-virtual-field-everywhere-in-gp/

Regards

David

[David david@winthropdc.com]

Up

0

Down

::

Hi Mary

The code is trying to connect directly to SQL rather than access a table so that does not identify the product.

The ability to set the SQLLastUser to nothing is in the Dex.ini Configuration window, not the Dex.ini Settings window. It is a different window under the Setup menu.

However, the only way to identify the product causing the issue now would be to temporarily remove products from the launch file.

Once the extra login issue is fixed, you probably will not need to clear SQLLastUser.

Please update GP Power Tools to build 31.3 as there are a few issues fixed.

Regards

David

[David david@winthropdc.com]

Up

0

Down

::

As for the Dexterity login dialog, rather than the Dynamics login dialog, this is caused by some custom code or ISV product attempting to access SQL tables before you have actually logged in.<div>

Please make sure your ISV products are up to date, including GP Power Tools. 😄 There is a hotfix available.

This dialog would not look at the Dex.ini settings you mentioned.

If you cancel that login, it should generate an error with a table name that would help identify the product that is causing the issue.

Regards

David

</div>

[David david@winthropdc.com]

Up

0

Down

::

Hi Mary

As you have GP Power Tools, you can check the two Dex.ini settings you mentioned in the Dex.ini Settings window.

However, if they are not achieving what you need, then use the Dex.ini Configuration window to clear the SQLLastUser Dex.ini settings in the Global Dex.ini.

Regards

David

[David david@winthropdc.com]

Up

0

Down

::

Community Summit is an annual event organized by Dynamic Communities.

There are also smaller virtual and live events organized by another organization under the DynamicsCon banner and they often run twice a year (spring and fall/autumn).

David

[David david@winthropdc.com]

Up

0

Down

::

Thanks John for your work on this great tool.

[David david@winthropdc.com]

Up

0

Down

::

Thanks for the plug.

We actually needed to update GP Power Tools code to allow the triggers to work in Service Mode. But that is a great addition to the products feature set.

David

[David david@winthropdc.com]

Up

0

Down

::

Hi Pam and team.

Please keep us all in the loop.

It is a very large cost to come from Australia and I hope to present at least one session. 😁

David

[David david@winthropdc.com]

Up

0

Down

::

GP Power Tools restores the legacy print dialog by default as the new dialog does not work well with GP.

It is an option that can be changed on the Dex.ini Settings window.