implement Password to modify any open batches.

(0) Share

Report

Posted on by Community Member

Not sure if this is do-able, but i doesn't hurt to ask.

Anyone know how to implement a password security code so anyone trying to modify any open batches get prompted for a security code/password?

Thanks in advance....!!

*This post is locked for comments

I have the same question (0)

All responses (5)

Answers (0)

Suggested answer

soma 24,410 on at

Like (0)

Report

I think field level security from GP will fulfill your requirement. Please have a look on the below link.

community.dynamics.com/.../field-level-security-in-gp-without-customization.aspx

Hope this helps!!!

Was this reply helpful? Yes No
L Vail 65,271 on at

Like (0)

Report

I presume you mean modify any transaction in any open batch, of any module. Or, do you have just specific modules? Some are easier than others.

Leslie

Was this reply helpful? Yes No
Suggested answer

Redbeard 12,931 on at

Like (0)

Report

Sergio -

Willoware.com has a Secure Batch by User feature as part of its Power Pack, which prevents users from accessing Sales Transactions in a “Secure Batch” that belongs to another user. Only the owner(s) of the “Secure Batch” can edit transactions in the batch, or assign new transactions to their Secure Batch.

I seem to remember a customization from IBIS, which performs much the same function. It may not be an exact fit, but I imagine either could be modified to fit your need. Having a prompt for a password on a batch is definitely a customization.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

That's correct, any module.... thank you!

Was this reply helpful? Yes No
Suggested answer

L Vail 65,271 on at

Like (0)

Report

This is a tough one if I'm thinking about it right. My scenario is that 'sally' is allowed to enter new transactions and save them, but once they are saved, she shouldn't be allowed to bring them back up and change them. It doesn't matter which batch she may have put them in - once saved, she can't change them in any way.

If you use batch approval and 'approve' the batch, nobody can edit any transaction in the batch, but this will not help, because you are really looking at this from the transaction point of view. Until that batch was 'approved', the transactions could still be changed.

Should the user be able to open a saved transaction to look at it or print it, but not be able to change it?

If they should not even be able to look at it, that might be a little easier. For instance, in payables you may be able to write some VBA script that checks the Vendor ID field whenever the doc number changes. If the Vendor ID isn't blank, it could be an existing document the user is trying to change, and you could prevent them from opening it. Better yet, some records have 'created dates' on them. These dates aren't populated until the document is saved. If the user opens a document that contains a created date, then you could disable the Save button and deal with the dialog asking if they want to save changes. Not all transaction types contain 'created' dates, but there is usually a field somewhere that will tell you whether the user is bringing up an existing document.

Unless there's something already out there, you'll need to deal with each transaction type uniquely. Hopefully, the product has already been built. Willoware might be able to modify their Batch program for less money than you expect. I'd check there first before I set out on a journey to write something new.

As you can see, there isn't an easy fix, but it's doable. You could do it with VBA, but it might be easier using Dexterity. Also, VBA will not be and is not supported by the Web client.

Kind regards,

Leslie

Was this reply helpful? Yes No