James
Forum Replies Created
-
Hi Kirsten,
Did you manage to figure out the mutation?
Just wondering as we are looking into this as well.
Thank you and kind regards,
James
-
If I remember correctly, this was released a couple of years ago and was very limited to who had access or who could get access.
We brought this module just after it was released and found it slightly bare. However this may be due to the limited access companies had to this module.
There are links to other modules for example RO, Contact manager however, they are simple links i.e. this RO is part of a contract, contract number shows on RO.
This has the potential to be very powerful and useful module wtihin Quantum.
It has been a long time since I have checked the module so there may be more changes.
If you have contracts stored in Excel, word and you want to move this into Quantum the module is ready.
I would recommend contacting Component Control for a demo or trial to ensure there are enough relevant fields to store your information.
-
We have recently upgraded to 12.1.4 and there was one issue which we encountered.
When you are in the parts master screen, some query windows such as “Customer Quote History” or “Vendor Quote History”, the “Entry Date” columns is mixed and no longer ordered. Example attached.
This seems to be an issue if the user has personalized their windows.
Click in the affect section and press ctrl+F10 and grab the top name after the last comma. I have attached a screen shot.
Use this name in the following statement:
select * from sys_queries where query_name = ‘REPAIR-SHORT’
Write down the SYSQR_AUTO_KEY.
You will also need to SYSUR_AUTO_KEY of the affected user:
select * from SYS_USERS where user_name = ‘*USERNAME*’
With both of these you can run the following statment:
Delete from sys_user_queries where sysqr_auto_key = 54 and sysur_auto_key =1430
You will have to do this per window affected. Ask the end-user to restart quantum to apply the change/fix.
-
Hello Stephen,
Please refer to “10.10.5” in this forum topic. If I remember correctly it stopped an email alert in event manager. Built-in alert “Posting Invoices” I think.
We use this to send invoices to our customers so it was quite important.
Unfortunately the tracker that was provided is still in the development queue however Component Control were quick to apply a workaround.
I wish I recorded what they did 🙁
Thank you and kind regards,
JV
-
Hello Ian,
A while ago we invested in some custom programming to add the shipping module on part warnings.
On all controlled parts we have enabled this warning and set the warning to “Restrict”.
We also created a daily procedure we checked all our export controls units to ensure they have this restriction in place.
With this restriction enabled on the part for the shipping module, end-users are unable to create a ship order or drag the ship order into a shipment. This is a full prevention and completely stops the unit from going out.
You can also limit which users receive this restriction i.e. everyone at Avtrade receives this restriction except for a few select people in our Technical Logistics Department.
This link between part warnings and user security is implemented via groups.
I.e. 1) create a blank template
2) When you are about to add the warning you wish to use, click groups and add the blank template. This creates the link, please see attached.
3) When you apply/append this blank template to an end-user they will see the restriction.
I hope this all makes sense.
Thanks,
JV
-
Hello All,
We have upgraded to 10.10.5 and everything was quite smooth.
Unfortunately we experienced the same issue with the posting invoice alert which sends the invoices to our customers via event manager.
I have spoken to CC and they have fixed the issue. They must have missed something because the alerts are generated however it didn’t know a location of where to move the alerts. I.e. they wouldn’t move from “generated” to “forwarded”.
They downloaded a .sql file (runnerv2.sql) which created a view called “VIEW_EMGR_RUNNER_MESSAGES”, they ran the “runner.exe” which fixed this issue.
If anyone comes across this, please refer to this ticket number: V704569 as they reported no notes were added to the tracker Gary mentioned 🙁
Thank you and kind regards,
JV
-
Thank you Gary, it is much appreciated. I will contact CC to discuss further with them.
@Sally, in regards to updating visual C++, may seem a silly question, are you referring to updating it on the Quantum Server? Or client machines?
Thank you and kind regards,
JV
-
Hello Gary,
In regards to the issue you had with emailing invoices out via event manager, can you advise the fix for this?
Or is this patched within 10.10.6?
We are planning on upgrading later this month.
Thank you and kind regards,
JV
-
Thank you Paul, it is much appreciated.
I will look into this further with the tables, and investigate further into the data needed in the sql insert statement.
Thank you,
JV
-
Hello All,
Has any one added a new user via automation? It would be interesting to see how this would work.
Thanks,
JV
-
Good Morning,
Here is the syntax I have used in the past:
FREQ=DAILY;BYDAY=MON,TUE,WED,THU,FRI;BYHOUR=8,10,12,14,16;BYMINUTE=0;BYSECOND=0
FREQ=HOURLY;BYMINUTE=0,2,4,6,8,10,12,14,16,18,20,22,24,26,28,30,32,34,36,38,40,42,44,46,48,50,52,54,56,58
Monthly and yearly does work however I tried BYDATE with this but this is not recognized.
FREQ=MONTHLY;BYDAY=MON
FREQ=YEARLY;BYMONTH=6,7,8,9,10,11,12
Not sure what it would be for last three days of the month.
Worst case you could run more than one event and schedule each with their own date (28, 29, 30, etc) each month (see attached)
Hope this helps in some way and would be interesting if someone has discovered how to do this by date?
JV
-
Gene Hembree wrote:
Good morning, It looks as if the Parts_Master table is linked to the Warning_Types table via the PNM_AUTO_KEY. Am I correct to say that to do a mass update you would have to write an SQL to add data to the Warning_Types table? Do I have the relationships defined correctly in the attachment? Does anyone have an example of an SQL that you have used to do a mass update of the part warnings?
Thank you,
Just to confirm your table linking and the relationships between them, you are correct. I have attached the basic’s you which also had and the links/joins are “left outer join’s”.
This is what I find works when creating reports for part warnings.
JV
-
Good Morning All,
A few weeks ago I had to mass insert part warnings for export control units.
I built a procedure with a cursor, below is the code, head to the bottom for more detail:
create or replace PROCEDURE IRU_WARN_RESTRICT
— warning_type 1 = Warning
— warning_type 2 = Restrict
— Module auto key 19 = Shipping Order
— Message auto key * = depends on when created
— WMS 10 = Warn Message
— WMS 74 = Restrict Message
–Input Variable
AS
CURSOR parts_check IS
SELECT PNM_AUTO_KEY
FROM PARTS_MASTER
WHERE (upper(ECC_NUMBER) LIKE upper(‘%7A101%’) or upper(ECC_NUMBER) LIKE upper(‘%7A103%’) or upper(“PARTS_MASTER”.”ECC_NUMBER”) LIKE upper(‘%7A103-A1%’) or upper(“PARTS_MASTER”.”ECC_NUMBER”) LIKE upper(‘%5A002-A-1-A%’));
parts_view parts_check%ROWTYPE; –set the Part typesview to match the data type
begin
open parts_check; — Open the cursor
Loop
FETCH parts_check INTO parts_view; — fetch the dataset from the cursor into the Parts_view variable
EXIT WHEN parts_check %NOTfOUND; –ends the loop if nothing is found
–RESTRICTION
UPDATE WARNING_TYPES SET WARNING_TYPE = 2 WHERE PNM_AUTO_KEY = parts_view.PNM_AUTO_KEY AND WMS_AUTO_KEY=74;
INSERT INTO warning_types (warning_type, WNM_AUTO_KEY, WMS_AUTO_KEY, pnm_auto_key) values (2, 19, 74, parts_view.”PNM_AUTO_KEY”); –Shipping Order
INSERT INTO warning_types (warning_type, WNM_AUTO_KEY, WMS_AUTO_KEY, pnm_auto_key) values (2, 20, 74, parts_view.”PNM_AUTO_KEY”); –Warehouse Transfer
end loop;
CLOSE parts_check; –close the cursor
commit; –commit the changes
end;
If the part warning already exists however it is set to warn and you want it to restrict, the update is what you will need.
If the part warning does not exist yet you will need to use the insert statement.
If you need to run this daily/on a schedule you will need to write more logic to only insert if the part warning is not there.
Any questions, please let me know and I hope this helps.
JV
-
Good Evening All,
To confirm version, this will be available in version 10.10.4.
JV
-
Hello Dan, This was happening on version 10.9.19 but we have upgraded to 10.9.23 since then.
Kind regards, JV
-
Hello Tim, I can confirm it is the built in “Posted Invoice Alert” email alert.
Kind regards, JV
-
No changes made to the Quantum Server prior the issue however I will keep a note of this just in case this happens again in the future, thank you 🙂
Kind regards, JV
-
@David, Thank you David for clarifying, I saw them go through only briefly.
They are working on the issue now but unfortunately they have advised it will require booking training with CC to learn how to apply the fix :/
Kind regards, JV
-
Update…
CC has looked at this for over 4-5 hours and partially fixed the issue. I have contacted them again to fully resolve this.
I have requested more information from them on how this is fixed. I will post here if they send another to help with this issue.
Kind regards, JV
-
@Henrik, @Abigail,
Thank you for the information I was unaware of this feature within Quantum. At the moment our structure is to keep both Quantum logins and AD logins separate from a security perspective.
However there may come a time where managing this may need to become more automated and from looking at the PDF this would be perfect especially with the encryption tick box I can see during setup.
@John, I’m assuming you could build on this even further by creating a standalone oracle DB which could link to quantum DB to somewhat eliminate the issue with running DataVersion?
Kind regards, JV
-
Hey Mike,
I’m unaware of a link between our Quantum and Active Directory however another look into the tables and I found: sys_user_db_session
Only has five columns: select * from sys_user_db_session
Might be something you can report on but it only displays users who currently have a session. Unfortunately I couldn’t see anything else 🙁
Kind regards, JV
-
Hey Mike,
I had a quick look and found the SYSLOG table which holds a little information. Unfortunately it doesn’t show the Quantum username but it does show the computer they are using.
This is what I used:
select log_id, log_dt_sys, log_dt_buh, log_host from syslog order by log_id desc
Kind regards, JV
-
How are you doing this?
We have tested this on 10.9.19 and it gives both options buy and exchange and they work correctly.
Has development got back to you on whether this has been fixed?
Thanks,
James
-
Thank you Nadim, this has fixed the issue.
Definitely something we won’t forget!
Much appreciated!
JV 🙂
-
Hello,
We have just completed our upgrade to 10.9.8 yesterday and here’s how it went:
We conducted some preliminary testing with each department beforehand with their daily processes. This was done on a replica VM with a copy of our main DB, no issues were spotted but always good to check to prevent anything that can stop the users from working.
During the upgrade of the client machines we ensured .NET was on the latest version. We also noticed when running Reg the update/installer would stop on most if not all machines due to the invoice module DLL.
The workaround was to let it fail and let it go to the login window. Once this appears with username and password, close Quantum. Re-add the reg to the shortcut and run as administrator; it then goes through clean. We removed the reg, run Quantum and client was upgraded.
Some clients did take longer than others but repeating the process or reinstalling Quantum also fixed the issue for us, this includes removing the Quantum DIR on the local install.
We also believe Windows 10 needed the tick box ticked for “Run As Administrator” on the shortcut properties or else Quantum didn’t like running the updates or running at all. There may be a local GP setting to prevent this and we will be looking into at soon.
This covers everything for the moment, if we experience anything else from the users, I will pass it along on here.
Thank you 🙂
-
Thank you, can’t believe I missed that, much appreciated 🙂
-
*******UPDATE*******
I have managed to get it working by replacing the label with a memo with the following code inside the OnPrint:
var
q : TOracleDataset;
begin
varSN.lines.clear;
q := TOracleDataset.Create(nil);
q.SetSession;
q.Sql.Text := ‘select stk.serial_number as ALL_SN from stock stk, stock_reservations str ‘+
‘where stk.stm_auto_key = str.stm_auto_key ‘+
‘and str.smd_auto_key = ‘ + SM_DETAIL[‘SMD_AUTO_KEY’] + ‘ order by stk.serial_number’ ;
q.Open;
while not q.eof do
begin
varSN.lines.add(q.FieldByName[‘ALL_SN’].AsString);
q.next;
end;
q.Free;
end;
The select statement pulls the serial numbers in individual rows and then the while loop prints each one. I also had to make the memo be able to stretch in the properties.
-
Hi Warren,
The company is not historical and PO’s are allowed. At the moment I am getting no data found and a generic error executing the trigger.
It references line 4 and 36 and I have tried adding the field referenced on 36 into the mutation in case it was a field that was required. No luck though.
I have raised with CC, just waiting for a response.
Thank you and kind regards,
James -
Hi Kirsten,
That’s quite interesting, I have been trying other areas of the Web API such as creating a PO header. However I am having issues, it seems these calls are to existing triggers within the DB. I suspect not all types have ! on all the fields that the trigger’s need.
In this example, I am receiving oracle errors from TI_PO_HEADER.
Would it be possible to get an extract of your mutation for the SO_HEADER? I would like to do a comparison to see whether it is what I suspect or whether I am writing the mutation for PO_HEADER incorrectly.
Thank you and kind regards,
James