Datasets:

pismacx
/

ai_assistant

Dataset card Data Studio Files Files and versions Community

Split (1)

train · 1k rows

Unnamed: 0 int64 0 999	0 stringlengths 258 77k
300	{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8732\n\n### Instruction:\n\xa0\r\n\r\n\xa0\r\n\r\n\xa0\r\n\r\nTo adjust calculations for technical results and FS printout.\r\n\r\nFS-M/0682 (ID 104706) - IBIP_DH\r\n\r\nFinancial statement document and FS new printout have different values for \'Average weight in gram\' (technical results) and \'Gewicht (kg)\' on FS printout\r\n\r\n!image-2023-03-10-10-05-17-666.png!\r\n\r\nOn SR there is different value \'Average wieght in kg\' than on FS document and FS printout\r\n !image-2023-03-10-10-07-28-811.png!\r\n\r\n\xa0\r\n\r\nValues for FS new printout are retrieved from invoices\r\n !image-2023-03-10-10-09-20-432.png!\r\n\r\n\xa0\n\n### Response:\n[\'Comment 1: ["[[email protected]]please confirm how it should be adjusted in system. * _Technical results on Financial statement document_ - field\\\'Average weight in gram\\\' is calculated:AverageWeight = (KgOfBroilersAL - WeightBridgeCorrectionAL + KgOfBroilersFL- WeightBridgeCorrectionFL)/(NumberOfBroilersFL,+ NumberOfBroilersAL)\|AverageWeight\|KgOfBroilersAL\|WeightBridgeCorrectionAL\|KgOfBroilersFL\|NumberOfBroilersFL\|NumberOfBroilersFL\|NumberOfBroilersAL\|\|2281\|42709.00\|431.0000\|0.00\|0.00\|0.00\|18537.0000\|To change: KgOfBroilersAL and KgOfBroilersFL should be value from \\\'Gross weight\\\' from Slaugtery Report documents instead of \\\'Net Weight\\\' * _Financial statement new printout_ - values in column \\\'Gewitcht\\\' is calculated from invoices (there is retrieved data from \\\'SLAC\\\' and \\\'VOER\\\') !image-2023-03-10-11-27-57-990.png!To change:Gewicht should be calculated as a sum of items \\\'SLAC\\\'\', \'Comment 2: \\\'VOER\\\' and also \\\'WGCO\\\'. * To confirm how should be treated value from Slaughtery Report \\\'Food discount in kg\\\'. Is this value included somewhere in invoices? (FS printout is based on invoices) Is this value should be included in technical results calculations: should be retrieved also in this calculationcurrent calcualtions:AverageWeight = (KgOfBroilersAL - WeightBridgeCorrectionAL + KgOfBroilersFL- WeightBridgeCorrectionFL)/(NumberOfBroilersFL,+ NumberOfBroilersAL)To change:AverageWeight = (KgOfBroilersAL - WeightBridgeCorrectionAL - Food discount in kg AL+ KgOfBroilersFL- WeightBridgeCorrectionFL - Food discount in kg FL)/(NumberOfBroilersFL,+ NumberOfBroilersAL)!image-2023-03-10-11-33-59-601.png!"\', \'Comment 3: "[[email protected]],we\\\'ve made changes in prinouts and technical results SQL procedures in test Intense environment (MAS NL & MAS BE). You can feel free to test it.Best regards\', \'Comment 4: Grzegorz"\', "Comment 5: \'Zmiana w procedurach:KR_Printout_FS2_Slaughtery,KR_Printout_FS2_Slaughtery_MAS_BE,KR_calculatetechresults,KR_calculatetechresults_MASBE.Opisane nazwą taska.\'", \'Comment 6: \\\'I have added two SR\\\\\\\'s and calculated the technical results twice.The green squares are correct. The red ones are not correct.For the "Aantal" you should only look at the SLAC. The quantity should be 100.000 and not 100.001.As well the "gewicht (kg)" is slightly different with 2,463 after my second test than the 2,462 on the line. Could you explain the difference to me?The average weight of all loaders in Intense on the technical results is also wrong. The Food discount and Weight bridge deviation are not in this figure yet. !image!\\\'\', "Comment 7: \'Hi [[email protected]],we made changes", \'Comment 8: because in the first requirements\', "Comment 9: we looked only for SLAC. Currently we are looking for \\\\\'SLAC\\\\\'", \'Comment 10: \\\\\\\'VOER\\\\\\\' and \\\\\\\'WGCO\\\\\\\' for quantity - "Aantal":!image-2023-03-15-08-47-25-435.png!So the value of "Aantal" 100 001,00 is correctly.The "Gem. gewitch" value on the prinout is from field "Average weight in gram" from Technical results:!image-2023-03-15-08-53-21-449.png!We made changes for this field in TR calculationyesterday as on the screen below:!image-2023-03-15-08-54-21-830.png!As I understand you\', \'Comment 11: also we need to change "Average weight FL" and "Average weight AL".The current calculation for these two fields is as follow:_Average weight FL: GrossWeightFL - WeightBridgeCorrectionFL/UnitsDeliveredFL__Average weight AL: GrossWeightAL - WeightBridgeCorrectionAL/UnitsDeliveredAL_To change:_Average weight FL: GrossWeightFL - WeightBridgeCorrectionFL - FoodDiscountInKgAL/UnitsDeliveredFL__Average weight AL: GrossWeightAL - WeightBridgeCorrectionAL - FoodDiscountInKgAL/UnitsDeliveredAL_I\\\\\\\'m waiting for your reply.Best regards,Grzegorz\\\'\', "Comment 12: \'You are completely right. You can make the changes as you propose.In addition: yesterday we came to the conclusion that we do not take the disapproves into account at the moment in the kg. This is new information for you. This means that the actual kg are a bit too high in the current calculations. To adjust this it must be something like:Average weight FL: (GrossWeightFL-AFKK-AFKO) - WeightBridgeCorrectionFL - FoodDiscountInKgAL/UnitsDeliveredFLAverage weight AL: (GrossWeightAL-AFKK-AFKO) - WeightBridgeCorrectionAL/UnitsDeliveredAL\'", "Comment 13: \'Ok", \'Comment 14: good. Right now\', \'Comment 15: we take the GrossWeight valuefrom Slaughtery report to calculation Technical Results:!image-2023-03-15-11-03-47-862.png!So\', \'Comment 16: where do we collect the values of "AFKK" and "AFKO"?\\\'\', \'Comment 17: "It would be best if you can base it on the PI\\\'s with these codes (see the attachment). Is that possible?Please note that these weights already have a minus in front of them. So it this will be the approach than we should do it like:Average weight FL: (GrossWeightFL+AFKK+AFKO) - WeightBridgeCorrectionFL - FoodDiscountInKgAL/UnitsDeliveredFLAverage weight AL: (GrossWeightAL+AFKK+AFKO) - WeightBridgeCorrectionAL/UnitsDeliveredAL!image-1!"\', \'Comment 18: "Ok\', \'Comment 19: If I correctly undestand\', \'Comment 20: we need to collect all elements from PI\\\'s with Item Code = \\\'AFKK\\\' / \\\'AFKO\\\' related to SR.I\\\'m working on it."\', "Comment 21: \'Yes indeed.\'", "Comment 22: \'[[email protected]],Could you look at the calculation again? I have some concerns. In the Financial Statement we had three Average weight: 1. Average weight first loaders", \'Comment 23: with calculation: _(GrossWeightFL - WeightBridgeCorrectionFL)/UnitsDeliveredFL_ 2. Average weight all loaders\', \'Comment 24: with calculation: _(GrossWeightAL- WeightBridgeCorrectionAL)/UnitsDeliveredAL_ 3. Average weight in gram\', \'Comment 25: with calculation: _(KgOfBroilersAL-WeightBridgeCorrectionAL)+(KgOfBroilersFL-WeightBridgeCorrectionFL)/(NumberOfBroilersF+NumberOfBroilersAL)1000_After modification\', \'Comment 26: we have: 1. Average weight first loaders\', \'Comment 27: with calculation: _((GrossWeightFL+(AFKK+AFKO)) - WeightBridgeCorrectionFL)-FoodDiscountInKgFL/UnitsDeliveredFL_ 2. Average weight all loaders\', \'Comment 28: with calculation: _((GrossWeightAL+(AFKK+AFKO)) - WeightBridgeCorrectionAL)/UnitsDeliveredAL_ 3. Average weight in gram\', \'Comment 29: with calculation: _(KgOfBroilersAL-WeightBridgeCorrectionAL-FoodDiscountInKgAL)+(KgOfBroilersFL-WeightBridgeCorrectionFL-FoodDiscountInKgFL)/(NumberOfBroilersF+NumberOfBroilersAL)1000_ When I recalculated Technical Results\', \'Comment 30: the "Average weight for first loaders" have strange value.Best regards\', "Comment 31: Grzegorz\'", "Comment 32: \'I think you are almost there. Some math brackets were not correct and you are missing the AFKK+AFKO in the total average weight in gram (please make sure that you do not extract (it are negative numbers) AFKK and AFKO twive", \'Comment 33: this must be distinquished between FL and AL as well:1. Average weight first loaders\', \'Comment 34: with calculation:((GrossWeightFL+AFKK+AFKO)) - WeightBridgeCorrectionFL -FoodDiscountInKgFL)/UnitsDeliveredFL2. Average weight all loaders\', \'Comment 35: with calculation:((GrossWeightAL+AFKK+AFKO)) - WeightBridgeCorrectionAL -FoodDiscountInKgAL)/UnitsDeliveredAL3. Average weight in gram\', "Comment 36: with calculation:(KgOfBroilersAL-WeightBridgeCorrectionAL-FoodDiscountInKgAL+AFKK+AFKO)+(KgOfBroilersFL-WeightBridgeCorrectionFL-FoodDiscountInKgFL+AFKK+AFKO)/ (NumberOfBroilersFL+NumberOfBroilersAL)1000Normally the average weight should be between 2 and 2,5kg.\'", "Comment 37: \'[[email protected]],the calculation for technical results has been changed. You can feel free to verify it in test Intense environment.Best regards,Grzegorz\'", \'Comment 38: \\\'Please see ID 79857:How can the Gewicht (kg) be 2,463 while the average from the table "Aflevergegevens slachterij" is 2,462. They should always be the same.Still the Aantal is 100.001 that should be 100.000..\\\'\', "Comment 39: \'See ID 79866. The AFKK is not in the calculation yet....Average in this case should be (200.000 - 10.000)/100.000.Please fix this.\'", \'Comment 40: "[[email protected]],ok\', \'Comment 41: I\\\'ve made modificaiton. You can verify it one more time.Best regards,Grzegorz"\', "Comment 42: \'I sitll see 2.000 as Average weight in gram and not 1.900.\'", "Comment 43: \'[[email protected]]the calculation model is look like:_(KgOfBroilersAL-WeightBridgeCorrectionAL-FoodDiscountInKgAL)+(KgOfBroilersFL-WeightBridgeCorrectionFL-FoodDiscountInKgFL)/(NumberOfBroilersF+NumberOfBroilersAL)1000_the values in MS SQL by parameter:!image-2023-03-16-14-01-52-244.png!Best regards,Grzegorz\'", \'Comment 44: "You still don\\\'t take AFKK and AFKO into account. Please take a good look at the previous posts in this task.Mitch van Bovene2 uur geledenSee ID 79866. The AFKK is not in the calculation yet....Average in this case should be (200.000 - 10.000)/100.000.Please fix this.-----------Mitch van BoveneGisteren 15:39I think you are almost there. Some math brackets were not correct and you are missing the AFKK+AFKO in the total average weight in gram (please make sure that you do not extract (it are negative numbers) AFKK and AFKO twive\', \'Comment 45: this must be distinquished between FL and AL as well:1. Average weight first loaders\', \'Comment 46: with calculation:((GrossWeightFL+AFKK+AFKO)) - WeightBridgeCorrectionFL -FoodDiscountInKgFL)/UnitsDeliveredFL2. Average weight all loaders\', \'Comment 47: with calculation:((GrossWeightAL+AFKK+AFKO)) - WeightBridgeCorrectionAL -FoodDiscountInKgAL)/UnitsDeliveredAL3. Average weight in gram\', \'Comment 48: with calculation:(KgOfBroilersAL-WeightBridgeCorrectionAL-FoodDiscountInKgAL+AFKK+AFKO)+(KgOfBroilersFL-WeightBridgeCorrectionFL-FoodDiscountInKgFL+AFKK+AFKO)/ (NumberOfBroilersFL+NumberOfBroilersAL)1000----------------------------------Grzegorz MaterlaGrzegorz MaterlaGisteren 11:37Ok\', \'Comment 49: If I correctly undestand\', \'Comment 50: we need to collect all elements from PI\\\'s with Item Code = \\\'AFKK\\\' / \\\'AFKO\\\' related to SR.I\\\'m working on it."\', "Comment 51: \'Yes", \'Comment 52: you have right\', "Comment 53: I was focused on Average weight FL and AL. The AFKK+AFKO parameter has been added to Average weight in gram and looks good.Changes made on both sector MAS NL and MAS BE.Best regards,Grzegorz\'", "Comment 54: \'Hi", \'Comment 55: The average weight is correct now “Gewicht (kg)” with 1,900. However on the line on the FS 2 I still see gem. Gew. 2,000 on the line. I will say it again: these numbers must match. Regards\', \'Comment 56: Mitch From:* Grzegorz Materla (Jira) <[email protected]> Sent: donderdag 16 maart 2023 14:56 To: Bovene\', "Comment 57: Mitch van <[email protected]> Subject: DGS-8732 Adjusting calculations and Financial statement (technical results) and FS printout \'", "Comment 58: \'Hi [[email protected]],on the printout in Slaughtery section", "Comment 59: the calculation of Gem.gew. is[KgSLACSUM]/[QuantitySLACSUM] (Gewicht/Aantal).Exactly with numbers: 200 000/100 000 = 2.000:!image-2023-03-17-09-28-20-686.png!So how to calculate this in the Slaughtery area? Data which we calculate Technical Results is different than on printout.Best regards,Grzegorz\'", \'Comment 60: \\\'The "Kg afkeur" needs to be distracted.So (200 000 - 10 000)/100 000 = 1.900.\\\'\', "Comment 61: \'We changed the calculation on printout. You can verify it.Best regards,Grzegorz\'", "Comment 62: \'Ok", "Comment 63: you can move this to PROD.\'", "Comment 64: \'[[email protected]],the printouts FS2 new and calculations of Technical Results for MAS NL and MAS BE have been moved into PROD Intense environment.Best regards", "Comment 65: Grzegorz\'", "Comment 66: \'Feed profit calculation adjustments with guarantees[^FW_ Foutieve berekening voerwinst.eml]\'", "Comment 67: \'Do kalkulacji Feed profit powinna być wliczana oryginalna wartość z faktur gwarancyjnych i powinno to wyglądać tak: (ABS(@AmountFL)+ABS(@AmountAL)) - ABS(@AmountOfFeed) -ABS(@AmountDOCNet) +Suma faktur gwarancyjnych\'", "Comment 68: \'Zrobione", "Comment 69: zgodnie zhttps://helpdesk.kotrak.com/browse/DGS-8641\'", "Comment 70: \'Do you expect something from us? I cannot open the attachment.\'", "Comment 71: \'{quote}Do you expect something from us? I cannot open the attachment.{quote}No", \'Comment 72: it was only mail with some discussion about calculations of feed profit\', \'Comment 73: but it has been handled in this task\', "Comment 74: https://helpdesk.kotrak.com/servicedesk/customer/portal/56/DGS-8641.Task is still open due to technical results changes and we can keep it open until we create new one or close linked tasks related to technical results.\'", "Comment 75: \'We need to change something on the new financial statement.On the old printout you can clearly see the unit price of 1.23. Hovewer on the new overview the unit prices are a bit lower. This is because the “Bedrag excl.” is divided by the “Kg afkeur””. However", "Comment 76: this amount also includes all disapproves (AFKK/Afkeur).The calculation of the prices must be the “Bedrag excl.” divided by the (“Gewicht”-“Kg afkeur” so that the unit price is € 1.23.!image-2!!image-3!\'", \'Comment 77: "I\\\'ve added this remarks to task with FS printout - [https://helpdesk.kotrak.com/servicedesk/customer/portal/56/DGS-8215]"\', "Comment 78: \'Unfortunately", \'Comment 79: the calculation for the average weight ("Gem. gew.) needs to be adjusted (again). No disapproves (AFKK) must be included in this.The calculation on the first line must be (69.200 / 35.411). Please make sure that also the calculation of the "Gewicht (kg)" in the technical results is changed. The AFKK needs to be excluded from this as well. !image-4!\\\'\', \'Comment 80: \\\'Another related change. In the column "Kg afkeur" we now see the kg\\\\\\\'s that are related to the AFKK (disapproves). Sometimes however De Heus compensates for this loss with the item code AFKH (disapproves for account of De Heus). In the column "Kg afkeur" we would like to see the weight related to (AFKK-AFKH). It is important that the AFKH always lowers the total weight for AFKK that the farmers needs to pay for.\\\'\', \'Comment 81: "{quote} # Average weight first loaders\', \'Comment 82: with calculation:((GrossWeightFL+AFKK+AFKO)) - WeightBridgeCorrectionFL -FoodDiscountInKgFL)/UnitsDeliveredFL2. Average weight all loaders\', \'Comment 83: with calculation:((GrossWeightAL+AFKK+AFKO)) - WeightBridgeCorrectionAL -FoodDiscountInKgAL)/UnitsDeliveredAL3. Average weight in gram\', "Comment 84: with calculation:(KgOfBroilersAL-WeightBridgeCorrectionAL-FoodDiscountInKgAL+AFKK+AFKO)+(KgOfBroilersFL-WeightBridgeCorrectionFL-FoodDiscountInKgFL+AFKK+AFKO)/ (NumberOfBroilersFL+NumberOfBroilersAL)1000{quote}This calculations have been changed and AFKK are not included right now like below. It\'s done in MAS NL and MAS BE sectors on Test environment.Please veriy.1. Average weight first loaders", \'Comment 85: with calculation:((GrossWeightFL{color:#de350b}-+AFKK-{color}+AFKO)) - WeightBridgeCorrectionFL -FoodDiscountInKgFL)/UnitsDeliveredFL2. Average weight all loaders\', \'Comment 86: with calculation:((GrossWeightAL{color:#de350b}-+AFKK-{color}+AFKO)) - WeightBridgeCorrectionAL -FoodDiscountInKgAL)/UnitsDeliveredAL3. Average weight in gram\', \'Comment 87: with calculation:(KgOfBroilersAL-WeightBridgeCorrectionAL-FoodDiscountInKgAL+AFKK+AFKO)+(KgOfBroilersFL-WeightBridgeCorrectionFL-FoodDiscountInKgFL{color:#de350b}-+AFKK-{color}+AFKO)/ (NumberOfBroilersFL+NumberOfBroilersAL)1000"\', "Comment 88: \'Zmodyfikowane wyliczanie w procedurach[dbo].[KR_calculatetechresults] i[dbo].[KR_calculatetechresults_MASBE] na bazie Testowej@WeightPISUMFL i @WeightPISUMAL!image-2023-04-07-13-23-41-722.png!\'", \'Comment 89: "After confirmation during today\\\'s call changes have been moved to production environmnent for MAS NL and MAS BE sectors."\', "Comment 90: \'can be closed\']"]\nRelated Issues:\n[\'DGS-8877\', \'DGS-8215\', \'DGS-8325\', \'DGS-8641\', \'DGS-8675\', \'DGS-8714\']\n\n### End'}
301	{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8731\n\n### Instruction:\nHi\r\nPlease help to check VT-6546/23 in Bien Hoa Plant. \r\n\r\n\n\n### Response:\n["Comment 1: [\'!image!\'", "Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", "Comment 3: \'HiPlease ignore this ticket . Tks you.\']"]\nRelated Issues:\n[]\n\n### End'}
302	{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8730\n\n### Instruction:\nHi\r\nWe found a weird situation about a PrO that were integrated to PCS even with status Canceled.\r\n\r\nThis is the case of PrO 0891070323004\r\nThis PrO were canceled but integrated. Looking with PCS supplier, no changes were done on PCS side.\r\nSo I decided to look through api.ProductionOrders and I found that the Status 3 (canceled) is present on the view. And Canceled PrO must not be imported to PCS.\r\n\r\nCould you please remove it from there? And all other plants?\r\n\r\nThank you very much!\n\n### Response:\n["Comment 1: [\'!0891070323004_integration_evidence.jpg\|thumbnail!!image!\'", "Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", "Comment 3: \'Dear Maicon,I have consulted this case and application behaved correctly. Information that PrO is cancelled", "Comment 4: should be sent to PCS.Regards\'", \'Comment 5: "Hi AleksandraI\\\'m sorry. I didn\\\'t get it. Why a cancelled PrO Should be sent to PCS?It is cancelled\', \'Comment 6: no need to produce it. In the specific case we reported\', \'Comment 7: the PrO were never confirmed\', \'Comment 8: so never should be sent to PCS.Could you please enlighten me?Thank you"\', "Comment 9: \'Hi Maicon,Sure.There is an option that allows to cancel PrO that are confirmed:!image-2023-03-10-13-53-39-766.png!We do not verify if cancelled PrO was canofirmed or not. That is why all events go to PCS. This is only a view.If you do not want to see cancelled PrO on the PCS list events", "Comment 10: a GDC task should be raised.Regards\'", \'Comment 11: "Hi AleksandraI still see this as a bug.Follow me: We have the configuration available: {{Sending unconfirmed PrO to PCS}}. This one is uncheckedWe also need thes {{ProdProductionOrderCancelConfirmed}} option to cancel confirmed PrO.But that is not the case of this DGS. The problem is that DHP configuration it\\\'s not working. DHP IS indeed sending unconfirmed PrO to PCS\', \'Comment 12: that is\', \'Comment 13: a mistake on DHP which is crashing cross configuration.Maybe [[email protected]] can help usThank you"\', "Comment 14: \'I have asked Wojciech for his opinion. However", "Comment 15: initial case related to cancelled PrO that you can see in PCS view. And that was consulted :)\'", \'Comment 16: \\\'[[email protected]],Even though you have unchecked the configuration entry "Sending unconfirmed PrO to PCS" are you able to see it in api.ProductionOrders in the PCS module?\\\'\', "Comment 17: \'Hi [[email protected]]In the case of reported PrO (0891070323004)", \'Comment 18: yes! I can see it in api.ProductionOrders in the PCS module.I understand that once the PrO is confirmed\', \'Comment 19: it will be available in api.ProductionOrders\', \'Comment 20: even if it is cancelled later\', \'Comment 21: afterall it was confirmed before.However\', "Comment 22: in the case of this 0891070323004 PrO was never confirmed as you can see in the attached screenshot of DHPlantPCSBusinessLogicEvents.dbo.ProductionOrdersThank you\'", "Comment 23: \'Z tego", \'Comment 24: co mówił Wojtek to powinni mieć tą funkcję włączoną\', "Comment 25: a nie mają. Przynajmniej dziś jak weszłam!image-2023-03-14-07-48-11-071.png!!image-2023-03-14-07-48-30-019.png!\'", "Comment 26: \'Requested PLR is in status Finished:!image-2023-03-14-08-09-43-570.png!Status 3 means finished", "Comment 27: cancelled for PLR is 5PrO is cancelled (status 3)!image-2023-03-14-08-30-03-498.png!Start Production był później niż cancel PrO!image-2023-03-14-08-36-17-056.png!!image-2023-03-14-08-33-20-007.png!\'", "Comment 28: \'!image-2023-03-14-10-25-18-805.png!!image-2023-03-14-10-26-15-302.png!!image-2023-03-14-10-28-17-687.png!\'", "Comment 29: \'Po PCSie eventy też poszły 7 marca!image-2023-03-14-13-55-02-272.png!!image-2023-03-14-13-58-13-389.png!\'", "Comment 30: \'Z tego", \'Comment 31: co Wojtuś mówi\', \'Comment 32: to:_{color:#0747a6}bo pewnie event z cancelem założył PrO w module PCSa. PCS pobrał sobie to PrO\', \'Comment 33: nie patrząc\', \'Comment 34: że ma status canceled i zaraportował produkcję do niego.trzeba dodać zmianę polegającą na tym\', \'Comment 35: żeby to anulowanie PrO działało tak\', \'Comment 36: że jak nie ma PrO w module PCS to event nic nie robi (nie dodaje anulowanego PrO; powinien tylko aktualizować status PrO o ile to PrO w module PCS już było){color}_{color:#172b4d}do dalszej knsultacji\', "Comment 37: czy będzie GDC{color}\'", \'Comment 38: "Po analizie widoku api.ProductioOrders: jest w nim warunek P.Status IN (2,3,4) OR (SELECT Value FROM dbo.Configuration WHERE [Key] = 4) = \\\'True\\\' \', \'Comment 39: który stwierdza\', \'Comment 40: że w widoku wystawiane są potwierdzone pro\', \'Comment 41: anulowane lub zmergowane albo wszystkie jeżeli konfiguracja na to pozwala.W ich przypadku założyli PrO\', \'Comment 42: trafiło ono do modułu PCS ale nie zostało wystawione w widoku. Po anulowaniu i zmianie statusu\', \'Comment 43: zgodnie z powyższym warunkiem zostało wystawione z flagą IsCancelled (flaga opisana w dokumentacji DHP3.0 - PCS_IntegrationCore. PCS zignorował tą flagę i utworzył na tej podstawie produkcję\', \'Comment 44: co jest błędem. Muszą walidować tą flagę po swojej stronie."\', "Comment 45: \'Hi [[email protected]],Mainly there are two conditions to display PrO in dbo.ProductionOrdersVIew# statuses: confirmed", \'Comment 46: merged\', \'Comment 47: and canceled# in case configuration for all production orders is turned on then all PrO statuses are displayedIt looks like in this case that the production order was created and sent to PCS (and was not visible in View). Later on\', "Comment 48: the production order was canceled and sent to PCS and available in the view with the flag IsCancelled=true (This flag is described in the documentation DHP3.0 - PCS_IntegrationCore). PCS ignored that flag and sent production.Our suggestion is to handle this flag in the PCS system in order to avoid such a situation in the future.If you want to change it somehow in the DHP please raise a GDC ticket for it.Regards\'", \'Comment 49: "Hi [[email protected]]I still see this is a bug\', \'Comment 50: actually a conflict of integration rules.The reported PrO has never been confirmed. Even being cancelled the PrO still unconfirmed. So there is one rule being ignored.But OK! I\\\'ll ask for PCS supplier to change on their side.You can close this taskThank you"\', "Comment 51: \'Hi Maicon,Thank you\']"]\nRelated Issues:\n[]\n\n### End'}
303	{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8729\n\n### Instruction:\nSome productions didn\'t integrated to DHC/ERP. We are missing productions:\r\nGLN2252-S30 0833070323006\r\nGLN2253-S30 0833070323007\r\nGLN2251-S15 0833070323008\r\n\r\nCould you check how many productions didn\'t integrated and fix integration?\r\nThank you\r\n\n\n### Response:\n["Comment 1: [\'Hello,\\\\r\\\\rWe are investigating your issue. We will inform you about the solution as soon as possible.\\\\r\\\\rRegards\\\\r\\\\r\'", "Comment 2: \'I could not see that PRL in DHC", \'Comment 3: I wanted to resend them from DHP but I cannot log to DHP and also server looks like it is not working\', \'Comment 4: could you please verify with your IT\', "Comment 5: if there are any network.infrastructure problems.!image-2023-03-09-22-03-14-599.png!!image-2023-03-09-22-02-45-793.png!\'", "Comment 6: \'!image-2023-03-09-22-04-36-215.png!\'", "Comment 7: \'Hi AgnieszkaI now can see them on DHC.You can close this task.Thank you very much!!image!\']"]\nRelated Issues:\n[]\n\n### End'}
304	{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8728\n\n### Instruction:\nwe have problem in production integration of lot number 0882080323005 and 0882080323004. Any dosage integrated, I asked PCS help and they answered that any error was find in their side. Please check attached the file with PCS information.\r\n\r\nCould you check why we have this error?\r\n\r\nThank you\n\n### Response:\n["Comment 1: [\'[^Cópia de 0882080323004 0882080323005.xlsx] _(14 kB)_\'", "Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", \'Comment 3: "pcs lotid=0882080323005\', \'Comment 4: - 73129id =\\\'dbc429f4-8370-4606-823c-836af7871991\\\'"\', \'Comment 5: "FROM [DHPlantPCSBusinessLogicMain].[dbo].[SqlApiRequestLog] where parameters like\\\'%73129%\\\'Production lot already exists. SELECT FROM [DHPlantProdBusinessLogicIntercontext].[dbo].[Errors]where message like \\\'%DBC429F4-8370-4606-823C-836AF7871991%\\\'"\', "Comment 6: \'!image-2023-03-10-10-35-10-822.png!\'", \'Comment 7: "brak stockunit na prodzie: select FROM [DHPlantProdBusinessLogicMain].[dbo].[StockUnits] where id=\\\'09f525d4-e4aa-4811-a20e-4aa65483e2a7\\\'"\', \'Comment 8: "Sytuacja wygglada tak że podany stock unit nie powstaje w module produkcja ponieważ wisi tam dla tego samego Barcode i Dostawy inny stock unit z inny datą i innym stockunitidFROM [DHPlantStockBusinessLogicMain].[dbo].[StockUnits] where id=\\\'09f525d4-e4aa-4811-a20e-4aa65483e2a7\\\'select *FROM [DHPlantProdBusinessLogicMain].[dbo].[StockUnits] where id=\\\'09f525d4-e4aa-4811-a20e-4aa65483e2a7\\\' or Barcode=\\\'88-W02781\\\'!image-2023-03-10-11-28-49-953.png!"\', "Comment 9: \'!image-2023-03-10-11-30-27-253.png!\'", "Comment 10: \'!image-2023-03-10-11-37-05-230.png!\'", "Comment 11: \'Oba loty dotyczą tego samego stock unit :09f525d4-e4aa-4811-a20e-4aa65483e2a7.Powiązanie zhttps://helpdesk.kotrak.com/browse/DGS-8467\'", "Comment 12: \'HelloThe issue relates to recreated barcodes. Problematic barcodes are quite old", "Comment 13: befor the version 8.3 has been upgraded.It is already underanalysis in task dgs-8467.I will inform you if there be any news.\']"]\nRelated Issues:\n[\'DGS-8467\']\n\n### End'}
305	{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8727\n\n### Instruction:\nHi\r\n\r\nCould you please update GDC_2-3weeks for Rio Claro on test and later, after approval, on Prod server?\r\n\r\nThank you\n\n### Response:\n["Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", "Comment 2: \'Dear [[email protected]] Estimation for the update to the latest 8.5 version – 12h", "Comment 3: including: * Backups: DB + App + generation of dbo.configurationBackup * Deployment + configs json (including Ack) * Scripts execution for IIS pools permissions * Validation of configuration * DHP verifications * HyperCare by deployment team not included * Update RC test env. * Update RC prod env.\'", "Comment 4: \'Dear [[email protected]]Estimation approved!You can update as soon as possible.Thank you\'", "Comment 5: \'[[email protected]]task można zamknąć. Realizacja na DIM.\'", "Comment 6: \'SR will be process in other project. This DGS has been closed.\']"]\nRelated Issues:\n[\'DGS-8844\']\n\n### End'}
306	{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8726\n\n### Instruction:\nthe VT-1347/23 didn\'t integrated to DHC.\r\n\r\nCould you check and fix it?\r\n\r\nThank you\n\n### Response:\n["Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", "Comment 2: \'Analiza wykazała że w dhcService i dhccountry znajdują się nagłowki dla danego dokuemntu", "Comment 3: brakuje natomiast jego elementów.Elementy jednego z zamówień zostały zarchiwizowane (status 20) i ponownie dodane do VT!image-2023-03-09-18-57-36-813.png!\'", \'Comment 4: "{code:java}select --distinct--o.MainBusinessPartnerId,o.TargetBusinessPartnerId,o.FinalBusinessPartnerId\', \'Comment 5: o.ForeignDocumentNumber,--oe.BusinessUnitId--,oe.No\', \'Comment 6: \\\'o\\\',o.,\\\'oe\\\',oe.,\\\'e\\\',e.* o.ForeignDocumentNumber,oe.no,e.No,e.Status,e.WeightValue,e.IsArchived,from DHPlantVCBusinessLogicMain.dbo.OrderElements oe join DHPlantVCBusinessLogicMain.dbo.Orders o on o.id=oe.id right join DHPlantVCBusinessLogicMain.dbo.VehicleTicketElements e on e.orderid=oe.id and e.OrderNo=oe.no where e.Id = \\\'B8C6C5F6-9ABF-43C2-AA29-66F84D81B254\\\'order by 3{code}{code:java}select top 100 BusinessPartnerId, from [Evolution_DHCountry].dbo.VehicleTickets where DocumentNumber like \\\'1347%2023/RC\\\'select top 100 * from Evolution_DHCService.dbo.VehicleTickets where DocumentNumber like \\\'1347%2023/RC\\\'{code}{code:java}select top 100 BusinessPartnerId,* from [Evolution_DHCountry].dbo.VehicleTicketElements where VehicleTicketId = \\\'45A4E3E0-D52C-48DE-853D-1A00BA9FA5FC\\\'select top 100 BusinessPartnerId,* from Evolution_DHCService.dbo.VehicleTicketElements where VehicleTicketId = \\\'45A4E3E0-D52C-48DE-853D-1A00BA9FA5FC\\\'{code}"\', \'Comment 7: "Przesyłając z poziomu DHP jest sukces\', \'Comment 8: !screenshot-2! ale nie ma nadal elementów VT jak Bartek wskazał wcześniej{code:java}select * FROM [Evolution_DHCService].[dbo].[VehicleTickets] where ExternalId=\\\'5000269\\\'SELECT * FROM [Evolution_DHCService].[dbo].[VehicleTicketElements] where VehicleTicketId=\\\'45A4E3E0-D52C-48DE-853D-1A00BA9FA5FC\\\' return foo;}{code} !screenshot-3! Już w Plancie jest mniej elementów w tabeli mapowań dla DHP:{code:java}SELECT * FROM [DHPlantIntegrationDhcServiceIdentityMapping].[dbo].[VehicleTicketElementIdentityMappings] where [PlantId]=\\\'B8C6C5F6-9ABF-43C2-AA29-66F84D81B254\\\'\\\\tSELECT * FROM [DHPlantVCBusinessLogicMain].[dbo].[VehicleTicketPackedDispatchElements] where id=\\\'B8C6C5F6-9ABF-43C2-AA29-66F84D81B254\\\'{code} !screenshot-1! "\', "Comment 9: \'VT is now in DHC !screenshot-4! \'", "Comment 10: \'Hi Piotr ,now is correct", "Comment 11: thank you.\'", "Comment 12: \'Thank you for confirmation.\']"]\nRelated Issues:\n[\'DAP-13422\']\n\n### End'}
307	{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8725\n\n### Instruction:\nIt should not be possible to edit a feed sale document whenever it has the status Archived.\r\n\r\nNow still Milas feed sales are imported whenever there is no new round available yet. This should not be the case.\r\n\r\nAlso it is still possible to manually add own wheat. That should not be possible when the feed sale document is in archived status as well.\n\n### Response:\n["Comment 1: [\'Hello,\\\\r\\\\rWe are investigating your issue. We will inform you about the solution as soon as possible.\\\\r\\\\rRegards\\\\r\\\\r\'", \'Comment 2: "Hi Mitch,{quote}Now still Milas feed sales are imported whenever there is no new round available yet. This should not be the case.{quote}It will be needed to modify it in integration. If there will be some exported feed sales from Milas and Feed sale in Intense will be archived we can block importing this feed sales to Intense and report error in webmethods. Then in Milas it should be reported to user somehow.Should we do changes in integration like described above?----{quote}It should not be possible to edit a feed sale document whenever it has the status Archived.{quote}{quote}Also it is still possible to manually add own wheat. That should not be possible when the feed sale document is in archived status as well.{quote}In Intense we have role which allow users edit any document\', \'Comment 3: it means that if someone has this right\', "Comment 4: can edit or adding some values on all documents (even archived).Now these users are in role \'Document edit\'.!image-2023-03-10-15-28-44-662.png!There is also second role which allows to edit documents in any state (there is you", \'Comment 5: Theo\', \'Comment 6: Richard\', \'Comment 7: Roderick\', \'Comment 8: Bessel\', \'Comment 9: Peter Moeliker\', \'Comment 10: Tim van Drie\', \'Comment 11: Martijn Meier).In that case these users can edit any document in Intense\', \'Comment 12: so this is consequence of this role. It works for all documents if someone has this right.Regards"\', "Comment 13: \'It will be needed to modify it in integration. If there will be some exported feed sales from Milas and Feed sale in Intense will be archived we can block importing this feed sales to Intense and report error in webmethods. Then in Milas it should be reported to user somehow.Should we do changes in integration like described above? --> It could happen that for instance round 2 is closed in the mean time but that there is still some feed send from Milas. Are we able to somehow post this on round 3 whenever round 3 is active?\'", "Comment 14: \'[[email protected]]chwilowo przypisuje na Ciebie nie wiem na ile to moze poczekac n Damiana ktory wczesniej to ogladal\'", \'Comment 15: "{quote}It will be needed to modify it in integration. If there will be some exported feed sales from Milas and Feed sale in Intense will be archived we can block importing this feed sales to Intense and report error in webmethods. Then in Milas it should be reported to user somehow.Should we do changes in integration like described above?{color:#172b4d}--> It could happen that for instance round 2 is closed in the mean time but that there is still some feed send from Milas. Are we able to somehow post this on round 3 whenever round 3 is active?{color}{quote}Do you mean that information sent from Milas should be somehow saved and should wait in some kind of queue for creating new Round 3 and Feed sale 3 document in Intense?I don\\\'t think that it\\\'s a good solution\', "Comment 16: because we don\'t have clear information if there will be in the future created Round 3 in Intense and we don\'t have some kind of temporary data which should be sent when something will happen in Intense (someone create Round 3). It will be needed to verify data in intense and xml files", \'Comment 17: so it will be difficult.When we block this feed sale sent from Milas and integration will not allow to add it in Intense\', \'Comment 18: it will be immediately clear information for user (if it will be handled in webmethods <-> Milas)."\', "Comment 19: \'!image-2023-03-21-13-36-37-537!Hi [[email protected]]", "Comment 20: please take a look at this diagram and confirm the requirements.\'", "Comment 21: \'Yes", \'Comment 22: this is clear. In stead of "Check for recent round numer for the same Contract" we should maybe same "Check for recent round numer for the same delivery customer".It can be that one contact has ended but for a next contact a new round has been created. It that case the food should be booked on that specific round. \\\'\', "Comment 23: \'Ok", \'Comment 24: just for confirmation:If we receive a message with round number 016951/0007/0001\', \'Comment 25: which is already in the archive\', \'Comment 26: and 016951/0007/0002 does not exist\', \'Comment 27: but\', \'Comment 28: for example\', \'Comment 29: 016951/0008/0001 is active\', "Comment 30: should we book a Feed on this round?\'", "Comment 31: \'Yes", "Comment 32: that is indeed the case.\'", \'Comment 33: "Hi [[email protected]],It\\\'s done. It can be tested on the IBIP_DH_TEST environment."\', \'Comment 34: "[[email protected]]we have an additional questions about some important details.1. What determine that Round is active? It should be status of document or that we have active processes (tasks) to this document?There is difference and these 2 parameters can be different. It can be case like this in this order:1 st process was closed and document has been sent to \\\'Archive\\\' 2 nd process has been started 3 rd process has been started 2 nd process wasclosed and document has been sent to \\\'Archive\\\'3 rd process is still open in Intense and document is possible to edit Status is \\\'Archive\\\' because field status is filled in when document is sent to \\\'Archive\\\' and last activity was sent document to Archive in 2 nd process.Example on IBIP_DH_TEST - round001056/0292/0001 !image-2023-04-03-10-51-27-904.png! !image-2023-04-03-10-51-52-679.png! 2.What should be done when someone feed sale will be sent from Milas to Intense and the same customer exists in other sectors.It could be case when there is no active rounds for customer with code807615 in MAS NL and there will be active round for customer807615 in OPPAS/PAS. In this case feed sale will be added to this round in Intense (last active round number for customer) When it will be based on customer from round number like 807615/0005/0001 \', \'Comment 35: first part of round is verified (customer code) and it will added to feed sale for this last round of this customer code."\', "Comment 36: \'1. Status of the document.2.What should be done when someone feed sale will be sent from Milas to Intense and the same customer exists in other sectors. --> It will never happen.\'", "Comment 37: \'Here is case on Prod database with customer code 807615 in more than one sector!image-2023-04-03-11-57-45-045.png!\'", "Comment 38: \'List of customer codes in more than 1 sector[^CustomerCodesInFewSectors.xlsx]\'", \'Comment 39: "We need to know what should be done in case when we have the same customer code in different sectors.In this case if customer exists in few sectors system looks for recent round for this customer\', \'Comment 40: then it\\\'s possible that feed sale line will be added to different sector than someone expects. In XML file there is no information about sector and system looking for customer from 1st part of round number like 807615/0005/0001."\', "Comment 41: \'Can be moved to PROD.\'", "Comment 42: \'It can be moved", "Comment 43: need to plan deployment.\']"]\nRelated Issues:\n[]\n\n### End'}
308	{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8724\n\n### Instruction:\nWe see code (883486100011) balance of Transaction and balance of Warehouse release are not same. Please refer attached for more details. \r\n\r\nCould you please help check why those are not same? This is Feed CDN.\n\n### Response:\n["Comment 1: [\'!image!!image-1!\'", "Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", "Comment 3: \'Difference is directly related with PW-00000004/01/23/Y1 document", \'Comment 4: and chossen date in Transaction > Chronologically list.!image-2023-03-09-14-15-21-959.png!Document issue date is set to 1st of January 2023 and its intake date is set to 1st of November 2023!image-2023-03-09-14-17-56-269.png!Choosen filter is set to Date wystawienia what means release date.Transaction > Chronologically list is created based onissue date. That mean when You choose Date: Date of rel./recive in filter both lists will have the same documents\', \'Comment 5: and quantity will be consistent.Please\', "Comment 6: let me know if the answer is sufficient for you. Do you expect any additional actions from us regarding this issue? Can we close this ticket?\'", "Comment 7: \'Hi", "Comment 8: I’m clear. Could we change date back 1st Nov 2023 to 1st Jan 2023 since date is wrong by user. Thanks\'", "Comment 9: \'Date has been changed. Please check.\'", "Comment 10: \'Now is ok. Please close the ticket. Thank you.\']"]\nRelated Issues:\n[]\n\n### End'}
309	{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8723\n\n### Instruction:\nWe didn\'t have opportunity to test it since the last request if it was changed properly until now so we need to change iban and swift code for all the Invoices for Kosovo just like in DGS-8547 request. Please check the screenshots. Thank you. \n\n### Response:\n["Comment 1: [\'!image!!image-1!\'", \'Comment 2: "Hello\', \'Comment 3: the printout is called \\\'KOSOVO Invoice test\\\' !screenshot-1! I added an entry as for the earlier printoutPlease check if it\\\'s supposed to look like this !screenshot-2! Regards."\', "Comment 4: \'Hello", \'Comment 5: it should be on all the invoices just like this as well. Whatever bank is under PAYMENT on the left side (Raiffeisen\', \'Comment 6: Sberbank etc …)\', "Comment 7: on all of them on the right side should be (AIK bank) as in the screenshot for all the Kosovo invoices.!image-2!\'", "Comment 8: \'Hello", "Comment 9: yes we will make the changes. Can i get the path as before then each printout to change?Like this: !screenshot-3! \'", "Comment 10: \'Your screenshot has correct path. Sales Export Invoice/Kosovo Invoice/View on the screen.\'", "Comment 11: \'Hi", "Comment 12: printout has been updated.\'", "Comment 13: \'Hi our invoicing dept has checked again and it is good path and the right side but they also want all the invoices on the left side under Payment to be the same AIK bank. We closed all the other bank accounts in other banks and now we need for them only this AIK banka data. Sorry for this inconvenience. \'", \'Comment 14: "Hi,sure I\\\'ll change it just now just move the bank account from right to left and leave one\', \'Comment 15: like below?Thank you. !screenshot-4! "\', "Comment 16: \'Yes on both sides the same AIK bank. Thank you!\'", \'Comment 17: "So only then will the left and right side be the same\', \'Comment 18: is this how the invoice should look like?Isn\\\'t one side enough? !screenshot-5! printout name for tests \\\'KOSOVO Invoice test\\\'"\', "Comment 19: \'Hi Piotr", "Comment 20: Our Invoicing dept wants to use again Raiffeisen and AIK bank and they want it on all the Kosovo invoice. Next time I will make meeting with them prior to create request because they change a lot. So left Raiffeisen and on the right AIK on all Kosovo invoices on the path Sales Export Invoice/Kosovo Invoice/View on the screen. Check the screenshots and thank you for your patience! Best regards.!image-3!!image-4!\'", "Comment 21: \'Hi", \'Comment 22: the printout has been modified as requested\', "Comment 23: please check and send feedback.Regards.\'", "Comment 24: \'It is all OK now. Please close this request and thank you. Best regards!\'", "Comment 25: \'Thank you for confirmation", "Comment 26: have a nice weekend.\']"]\nRelated Issues:\n[]\n\n### End'}
310	{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8722\n\n### Instruction:\nHello, \r\n\r\nyesterday I found out that we are able to post a regular document without selecting a round number.\r\nI understood that for all sectors this should be obligatory for financed and regular documents.\r\n\r\nI heard that trade is different, no round selection there, but document flow is different too.\r\n\r\nKR,\r\nChristine\n\n### Response:\n["Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", \'Comment 2: "Hello,I\\\'ve chcecked configuration in Intense.Only for Purchase Invoices with Registered type can be processed little differently and you should be able to sent it without approval flow (directly from state Entry to Archive). For trade type of invoice flow is normal like other invoices.Indeed Full round number are not mandatory on SI and PI invoices. We can add some validation\', \'Comment 3: maybe the best will be validation when invoice is sent to Archive and if \\\'Full number\\\' (Round) will be empty we can block document and not allow sent it to Archive.@MitchShould we adjust system and make mandatory on invoices field with Round number (\\\'Full number\\\')?Maybe it should be also implemented some conditions when invoice should has filled Round number.I see a lot of invoices in MAS NL (PI or SI) that don\\\'t have filled this field - for now around 2500 form13800 invoices in total. Most of these 2500 are regular. I\\\'m not sure that is good solution to make mandatory this field on invoices and if this will be helpful and allow to avoid some situations.Regards"\', \'Comment 4: "Should we adjust system and make mandatory on invoices field with Round number (\\\'Full number\\\')? --> Yes please. Indeed before we send them to archive they should have a full number.Let\\\'s investigate the empty ones. Can you send me a report? I would like to investigat e them and see why they do not have a full number on them."\', "Comment 5: \'The report should consist invoices from all other sectors as well.\'", "Comment 6: \'{color:black}Damian,{color} {color:black}{color} {color:black}Thanks for your remark and check!{color} {color:black}For NAS all our regular postings should have a round number.{color} {color:black}{color} {color:black}I understood from the MAS colleagues that our BE (boer BE: 888888) transactions and trade transaction are the exception to the rule.{color} {color:black}But in all other transactions when a regular posting is created", \'Comment 7: we have to select a round number. Otherwise posting will not appear on the round.{color} {color:black}{color} {color:black}{color} \| \|{color:#000001} Metvriendelijkegroet,{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:#000001}{color} \| \| \| \|{color:#000001} Christinede{color} \|{color:#000001} {color} \|{color:#000001} Jong{color} \| {color:#000001}MedewerkerContractadministratie{color} \| \| \|{color:black}{color} {color:black}{color}{color:windowtext}{color}{color:black}{color}!image001!{color:black} <[https://www.de-heus.nl/]>{color} \| \| {color:#006FB7} DEHEUSVOEDERSB.V.{color} \| \| \| \|{color:#000001} Postbus396 6710BJEde \\\\u200b{color} \| \|{color:#000001} Rubensstraat175 6717VEEde \\\\u200b{color} \| \| \|{color:#000001} T:0318675567{color} \| {color:#000001}KvK14626985{color} _{color:#000001} _Opdite‑mailberichteneventuelebijlage(n)isdedisclaimervantoepassing_ _gepubliceerdopdewebsitevan_ {color}[{color:#000001}{color}{color:#000001} _+ DeHeusVoeders+_{color}{color:#000001} {color}\|https://www.de-heus.nl/privacy-beleid]{color:#000001} _._{color}_ \| \| !image002! <[https://www.facebook.com/deheusvoeders]>{color:black}{color} \| \| !image003! <[https://twitter.com/de_heus_voeders]>{color:black}{color} \| \| !image004! <[https://www.youtube.com/channel/UCqkrGebUlFowgumurz-abxQ]>{color:black}{color} \| \| !image005! <[https://www.linkedin.com/company/de-heus-voeders-b-v-/]>{color:black}{color} \| Van: Damian Świstek (Jira) <[email protected]> Verzonden: vrijdag 10 maart 2023 13:09 Aan: Jong\', "Comment 8: Christine de <[email protected]> Onderwerp: DGS-8722 Round number selection should be obligatory \'", "Comment 9: \'Do przygotowania raport z dokumentów faktur", "Comment 10: które nie mają uzupełnionych rund.Do dodania walidacja przy przesyłaniu faktur do archiwum.\'", "Comment 11: \'Is this closed?\'", "Comment 12: \'{color:black}Hi Mitch,{color} {color:black} No action seen from Kotrak after my remark from{color} {color:#707070}10/Mar/23 13:49{color} {color:black}{color} {color:black}{color} \| \|{color:#000001} Metvriendelijkegroet,{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:#000001}{color} \| \| \| \|{color:#000001} Christinede{color} \|{color:#000001} {color} \|{color:#000001} Jong{color} \| {color:#000001}MedewerkerContractadministratie{color} \| \| \|{color:black}{color} {color:black}{color}{color:windowtext}{color}{color:black}{color}!image001!{color:black} <[https://www.de-heus.nl/]>{color} \| \| {color:#006FB7} DEHEUSVOEDERSB.V.{color} \| \| \| \|{color:#000001} Postbus396 6710BJEde \\\\u200b{color} \| \|{color:#000001} Rubensstraat175 6717VEEde \\\\u200b{color} \| \| \|{color:#000001} T:0318675567{color} \| {color:#000001}KvK14626985{color} _{color:#000001} _Opdite‑mailberichteneventuelebijlage(n)isdedisclaimervantoepassing_ _gepubliceerdopdewebsitevan_ {color}[{color:#000001}{color}{color:#000001} _+ DeHeusVoeders+_{color}{color:#000001} {color}\|https://www.de-heus.nl/privacy-beleid]{color:#000001} _._{color}_ \| \| !image002! <[https://www.facebook.com/deheusvoeders]>{color:black}{color} \| \| !image003! <[https://twitter.com/de_heus_voeders]>{color:black}{color} \| \| !image004! <[https://www.youtube.com/channel/UCqkrGebUlFowgumurz-abxQ]>{color:black}{color} \| \| !image005! <[https://www.linkedin.com/company/de-heus-voeders-b-v-/]>{color:black}{color} \| Van: Mitch van Bovene (Jira) <[email protected]> Verzonden: dinsdag 21 maart 2023 11:46 Aan: Jong", "Comment 13: Christine de <[email protected]> Onderwerp: DGS-8722 Round number selection should be obligatory \'", \'Comment 14: "Only in NAS sector should be implemented validation when document SI or PI only with type \\\'Regular\\\' has empty Round number (\\\'Full number\\\')?Or it should be implemented to all invoices in all sectors and then should be verified and it shouldn\\\'t be possible to send to \\\'Archive\\\' whenRound number (\\\'Full number\\\') is empty?We\\\'ll prepare mentioned before report and it will be possible to analyse invoices."\', \'Comment 15: "[[email protected]]do przygotowania raport spod bazy do Excela ze wszystkimi fakturami - SI i PI ze wszystkich sektorów\', \'Comment 16: które mają pustę rundę (\\\'Full number\\\')."\', "Comment 17: \'{color:black}Hi Damian,{color} {color:black}{color} {color:black}Make it only for NAS. In MAS there are exceptions.{color} {color:black}Thanks for your action.{color} {color:black}{color} {color:black}{color} \| \|{color:#000001} Metvriendelijkegroet,{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:#000001}{color} \| \| \| \|{color:#000001} Christinede{color} \|{color:#000001} {color} \|{color:#000001} Jong{color} \| {color:#000001}MedewerkerContractadministratie{color} \| \| \|{color:black}{color} {color:black}{color}{color:windowtext}{color}{color:black}{color}!image001!{color:black} <[https://www.de-heus.nl/]>{color} \| \| {color:#006FB7} DEHEUSVOEDERSB.V.{color} \| \| \| \|{color:#000001} Postbus396 6710BJEde \\\\u200b{color} \| \|{color:#000001} Rubensstraat175 6717VEEde \\\\u200b{color} \| \| \|{color:#000001} T:0318675567{color} \| {color:#000001}KvK14626985{color} _{color:#000001} _Opdite‑mailberichteneventuelebijlage(n)isdedisclaimervantoepassing_ _gepubliceerdopdewebsitevan_ {color}[{color:#000001}{color}{color:#000001} _+ DeHeusVoeders+_{color}{color:#000001} {color}\|https://www.de-heus.nl/privacy-beleid]{color:#000001} _._{color}_ \| \| !image002! <[https://www.facebook.com/deheusvoeders]>{color:black}{color} \| \| !image003! <[https://twitter.com/de_heus_voeders]>{color:black}{color} \| \| !image004! <[https://www.youtube.com/channel/UCqkrGebUlFowgumurz-abxQ]>{color:black}{color} \| \| !image005! <[https://www.linkedin.com/company/de-heus-voeders-b-v-/]>{color:black}{color} \| Van: Damian Świstek (Jira) <[email protected]> Verzonden: dinsdag 21 maart 2023 12:52 Aan: Jong", "Comment 18: Christine de <[email protected]> Onderwerp: DGS-8722 Round number selection should be obligatory \'", "Comment 19: \'[^PI,SI without rounds-2.csv]\'", "Comment 20: \'select Doc_FullNumber ,doc_id AS ID,pi.DIC_SValue as [Type_Purchase],si.DIC_SValue as [Type_Sales],Frm_FullName AS SECTOR from Documents left join Firms on Doc_FrmID=frm_id left join dictionaries as pi on pi.dic_id=Doc_IntColumn10 left join dictionaries as si on si.dic_id=Doc_IntColumn11where Doc_DdfID in (13,14,24,25,28,29,42,43,51,52,57,58) and Doc_IntColumn12 is null\'", "Comment 21: \'{color:black}Please only make it obligatory in NAS.{color} {color:black}MAS has exceptions.{color} {color:black}{color} {color:black}This csv mostly shows MAS documents.{color} {color:black}I will change the NAS if not already done.{color} {color:black}{color} {color:black}{color} {color:black}{color} {color:black}{color} \| \|{color:#000001} Metvriendelijkegroet,{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:#000001}{color} \| \| \| \|{color:#000001} Christinede{color} \|{color:#000001} {color} \|{color:#000001} Jong{color} \| {color:#000001}MedewerkerContractadministratie{color} \| \| \|{color:black}{color} {color:black}{color}{color:windowtext}{color}{color:black}{color}!image001!{color:black} <[https://www.de-heus.nl/]>{color} \| \| {color:#006FB7} DEHEUSVOEDERSB.V.{color} \| \| \| \|{color:#000001} Postbus396 6710BJEde \\\\u200b{color} \| \|{color:#000001} Rubensstraat175 6717VEEde \\\\u200b{color} \| \| \|{color:#000001} T:0318675567{color} \| {color:#000001}KvK14626985{color} _{color:#000001} _Opdite‑mailberichteneventuelebijlage(n)isdedisclaimervantoepassing_ _gepubliceerdopdewebsitevan_ {color}[{color:#000001}{color}{color:#000001} _+ DeHeusVoeders+_{color}{color:#000001} {color}\|https://www.de-heus.nl/privacy-beleid]{color:#000001} _._{color}_ \| \| !image002! <[https://www.facebook.com/deheusvoeders]>{color:black}{color} \| \| !image003! <[https://twitter.com/de_heus_voeders]>{color:black}{color} \| \| !image004! <[https://www.youtube.com/channel/UCqkrGebUlFowgumurz-abxQ]>{color:black}{color} \| \| !image005! <[https://www.linkedin.com/company/de-heus-voeders-b-v-/]>{color:black}{color} \| Van: Tomasz Zygoń (Jira) <[email protected]> Verzonden: dinsdag 21 maart 2023 13:26 Aan: Jong", "Comment 22: Christine de <[email protected]> Onderwerp: DGS-8722 Round number selection should be obligatory !image006.gif!\'", \'Comment 23: "{color:#000000}Hi [[email protected]],{color}{quote}{color:#000000}Make it only for NAS. In MAS there are exceptions.{color}{quote}{color:#000000}We can do a validation for NAS sector only for \\\'Regular\\\' types of PI\\\'s and SI\\\'s.Is it right condtion? {color}{color:#000000}It will be verified when document is sent to \\\'Archive\\\'.{color}[[email protected]]Should we do also validations to other sectors or do you need to analyse the report at first?Here is a report with invoices with empty rounds.[^PI,SI without rounds-2.csv]"\', "Comment 24: \'{color:black}Hi Tomasz,{color} {color:black}{color} {color:black}I am not able to make corrections so this is what a checked.{color} \|{color:black} Doc_fullnumber{color} \|{color:black} Doc_id{color} \|{color:black} Type of purchase{color} \|{color:black} Type of sale{color} \|{color:black} Sector{color} \|{color:black} Remark{color} \| \|{color:black} PI-RLN/2022/0168{color} \|{color:black} 34832{color} \|{color:black} Regular purchase{color} \|{color:black} NULL{color} \|{color:black} NAS{color} \|{color:black} Cancelled{color} \| \|{color:black} SI-RLN/2022/0181{color} \|{color:black} 36658{color} \|{color:black} NULL{color} \|{color:black} Regular sale{color} \|{color:black} NAS{color} \|{color:black} Conversiepost?{color} \| \|{color:black} SI-RLN/2022/0185{color} \|{color:black} 36662{color} \|{color:black} NULL{color} \|{color:black} Regular sale{color} \|{color:black} NAS{color} \|{color:black} Conversiepost?{color} \| \|{color:black} SI-RLN/2022/0186{color} \|{color:black} 36663{color} \|{color:black} NULL{color} \|{color:black} Regular sale{color} \|{color:black} NAS{color} \|{color:black} Conversiepost?{color} \| \|{color:black} SI-RLN/2022/0193{color} \|{color:black} 36670{color} \|{color:black} NULL{color} \|{color:black} Regular sale{color} \|{color:black} NAS{color} \|{color:black} Conversiepost?{color} \| \|{color:black} PI-RLN/2022/0368{color} \|{color:black} 54130{color} \|{color:black} Regular purchase{color} \|{color:black} NULL{color} \|{color:black} NAS{color} \|{color:black} Cancelled{color} \| \|{color:black} PI-RLN/2022/0389{color} \|{color:black} 56907{color} \|{color:black} Regular purchase{color} \|{color:black} NULL{color} \|{color:black} NAS{color} \|{color:black} Cancelled{color} \| \|{color:black} PI-RLN/2022/0396{color} \|{color:black} 57265{color} \|{color:black} Regular purchase{color} \|{color:black} NULL{color} \|{color:black} NAS{color} \|{color:black} Cancelled{color} \| \|{color:black} SI-RTN/2022/0131{color} \|{color:black} 57945{color} \|{color:black} NULL{color} \|{color:black} Registered sale{color} \|{color:black} NAS{color} \|{color:black} should be on 101662/0029/0001{color} \| \|{color:black} SI-RTN/2023/0216{color} \|{color:black} 92252{color} \|{color:black} NULL{color} \|{color:black} Registered sale{color} \|{color:black} NAS{color} \|{color:black} should be on 100893/0012/0001{color} \| \|{color:black} PI-RLN/2023/0402{color} \|{color:black} 107876{color} \|{color:black} Regular purchase{color} \|{color:black} NULL{color} \|{color:black} NAS{color} \|{color:black} is posted today on fictive customer with round number{color} \| \|{color:black} PI-RLN/2023/0403{color} \|{color:black} 107877{color} \|{color:black} Regular purchase{color} \|{color:black} NULL{color} \|{color:black} NAS{color} \|{color:black} is posted today on round number 102079/0061/0001{color} \| {color:black}{color} {color:black}The cancelled ones should be disregard.{color} {color:black}Conversion post => Conversiepost.{color} [{color:black}@Bovene", \'Comment 25: Mitch van{color}\|mailto:[email protected]]{color:black} is it correct that these are posted as regulars?{color} {color:black}{color} {color:black}Could you/or someone change my highlighted yellow 2 lines? It should be on the round mentioned in column remark.{color} {color:black}Thanks!{color} {color:black}{color} \| \|{color:#000001} Metvriendelijkegroet,{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:#000001}{color} \| \| \| \|{color:#000001} Christinede{color} \|{color:#000001} {color} \|{color:#000001} Jong{color} \| {color:#000001}MedewerkerContractadministratie{color} \| \| \|{color:black}{color} {color:black}{color}{color:windowtext}{color}{color:black}{color}!image001!{color:black} <[https://www.de-heus.nl/]>{color} \| \| {color:#006FB7} DEHEUSVOEDERSB.V.{color} \| \| \| \|{color:#000001} Postbus396 6710BJEde \\\\u200b{color} \| \|{color:#000001} Rubensstraat175 6717VEEde \\\\u200b{color} \| \| \|{color:#000001} T:0318675567{color} \| {color:#000001}KvK14626985{color} _{color:#000001} _Opdite‑mailberichteneventuelebijlage(n)isdedisclaimervantoepassing_ _gepubliceerdopdewebsitevan_ {color}[{color:#000001}{color}{color:#000001} _+ DeHeusVoeders+_{color}{color:#000001} {color}\|https://www.de-heus.nl/privacy-beleid]{color:#000001} _._{color}_ \| \| !image002! <[https://www.facebook.com/deheusvoeders]>{color:black}{color} \| \| !image003! <[https://twitter.com/de_heus_voeders]>{color:black}{color} \| \| !image004! <[https://www.youtube.com/channel/UCqkrGebUlFowgumurz-abxQ]>{color:black}{color} \| \| !image005! <[https://www.linkedin.com/company/de-heus-voeders-b-v-/]>{color:black}{color} \| Van: Jong\', \'Comment 26: Christine de Verzonden: dinsdag 21 maart 2023 13:41 Aan: [email protected] Onderwerp: RE: DGS-8722 Round number selection should be obligatory {color:black}Please only make it obligatory in NAS.{color} {color:black}MAS has exceptions.{color} {color:black}{color} {color:black}This csv mostly shows MAS documents.{color} {color:black}I will change the NAS if not already done.{color} {color:black}{color} {color:black}{color} {color:black}{color} {color:black}{color} \| \|{color:#000001} Metvriendelijkegroet,{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:#000001}{color} \| \| \| \|{color:#000001} Christinede{color} \|{color:#000001} {color} \|{color:#000001} Jong{color} \| {color:#000001}MedewerkerContractadministratie{color} \| \| \|{color:black}{color} {color:black}{color}{color:windowtext}{color}{color:black}{color}!image001!{color:black} <[https://www.de-heus.nl/]>{color} \| \| {color:#006FB7} DEHEUSVOEDERSB.V.{color} \| \| \| \|{color:#000001} Postbus396 6710BJEde \\\\u200b{color} \| \|{color:#000001} Rubensstraat175 6717VEEde \\\\u200b{color} \| \| \|{color:#000001} T:0318675567{color} \| {color:#000001}KvK14626985{color} _{color:#000001} _Opdite‑mailberichteneventuelebijlage(n)isdedisclaimervantoepassing_ _gepubliceerdopdewebsitevan_ {color}[{color:#000001}{color}{color:#000001} _+ DeHeusVoeders+_{color}{color:#000001} {color}\|https://www.de-heus.nl/privacy-beleid]{color:#000001} _._{color}_ \| \| !image002! <[https://www.facebook.com/deheusvoeders]>{color:black}{color} \| \| !image003! <[https://twitter.com/de_heus_voeders]>{color:black}{color} \| \| !image004! <[https://www.youtube.com/channel/UCqkrGebUlFowgumurz-abxQ]>{color:black}{color} \| \| !image005! <[https://www.linkedin.com/company/de-heus-voeders-b-v-/]>{color:black}{color} \| Van: Tomasz Zygoń (Jira) <[[email protected]\|mailto:[email protected]]> Verzonden: dinsdag 21 maart 2023 13:26 Aan: Jong\', "Comment 27: Christine de <[[email protected]\|mailto:[email protected]]> Onderwerp: DGS-8722 Round number selection should be obligatory !image006.gif!\'", "Comment 28: \'{color:black}Hi Damian,{color} {color:black}{color} {color:black}Yes", \'Comment 29: but the registered should also be obligatory as the registration invoices are on the round in Intense.{color} {color:black}{color} \| \|{color:#000001} Metvriendelijkegroet,{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:#000001}{color} \| \| \| \|{color:#000001} Christinede{color} \|{color:#000001} {color} \|{color:#000001} Jong{color} \| {color:#000001}MedewerkerContractadministratie{color} \| \| \|{color:black}{color} {color:black}{color}{color:windowtext}{color}{color:black}{color}!image001!{color:black} <[https://www.de-heus.nl/]>{color} \| \| {color:#006FB7} DEHEUSVOEDERSB.V.{color} \| \| \| \|{color:#000001} Postbus396 6710BJEde \\\\u200b{color} \| \|{color:#000001} Rubensstraat175 6717VEEde \\\\u200b{color} \| \| \|{color:#000001} T:0318675567{color} \| {color:#000001}KvK14626985{color} _{color:#000001} _Opdite‑mailberichteneventuelebijlage(n)isdedisclaimervantoepassing_ _gepubliceerdopdewebsitevan_ {color}[{color:#000001}{color}{color:#000001} _+ DeHeusVoeders+_{color}{color:#000001} {color}\|https://www.de-heus.nl/privacy-beleid]{color:#000001} _._{color}_ \| \| !image002! <[https://www.facebook.com/deheusvoeders]>{color:black}{color} \| \| !image003! <[https://twitter.com/de_heus_voeders]>{color:black}{color} \| \| !image004! <[https://www.youtube.com/channel/UCqkrGebUlFowgumurz-abxQ]>{color:black}{color} \| \| !image005! <[https://www.linkedin.com/company/de-heus-voeders-b-v-/]>{color:black}{color} \| Van: Damian Świstek (Jira) <[email protected]> Verzonden: dinsdag 21 maart 2023 13:51 Aan: Jong\', "Comment 30: Christine de <[email protected]> Onderwerp: DGS-8722 Round number selection should be obligatory !image006.gif!\'", "Comment 31: \'Hi Christine", \'Comment 32: I have no idea to be honest. If you think they should have been financed than we need to change them. Regards\', \'Comment 33: Mitch Van: Jong\', \'Comment 34: Christine de <[email protected]> Verzonden: dinsdag 21 maart 2023 14:00 Aan: [email protected]; Bovene\', \'Comment 35: Mitch van <[email protected]> Onderwerp: RE: DGS-8722 Round number selection should be obligatory {color:black}Hi Tomasz,{color} {color:black}{color} {color:black}I am not able to make corrections so this is what a checked.{color} \|{color:black} Doc_fullnumber{color} \|{color:black} Doc_id{color} \|{color:black} Type of purchase{color} \|{color:black} Type of sale{color} \|{color:black} Sector{color} \|{color:black} Remark{color} \| \|{color:black} PI-RLN/2022/0168{color} \|{color:black} 34832{color} \|{color:black} Regular purchase{color} \|{color:black} NULL{color} \|{color:black} NAS{color} \|{color:black} Cancelled{color} \| \|{color:black} SI-RLN/2022/0181{color} \|{color:black} 36658{color} \|{color:black} NULL{color} \|{color:black} Regular sale{color} \|{color:black} NAS{color} \|{color:black} Conversiepost?{color} \| \|{color:black} SI-RLN/2022/0185{color} \|{color:black} 36662{color} \|{color:black} NULL{color} \|{color:black} Regular sale{color} \|{color:black} NAS{color} \|{color:black} Conversiepost?{color} \| \|{color:black} SI-RLN/2022/0186{color} \|{color:black} 36663{color} \|{color:black} NULL{color} \|{color:black} Regular sale{color} \|{color:black} NAS{color} \|{color:black} Conversiepost?{color} \| \|{color:black} SI-RLN/2022/0193{color} \|{color:black} 36670{color} \|{color:black} NULL{color} \|{color:black} Regular sale{color} \|{color:black} NAS{color} \|{color:black} Conversiepost?{color} \| \|{color:black} PI-RLN/2022/0368{color} \|{color:black} 54130{color} \|{color:black} Regular purchase{color} \|{color:black} NULL{color} \|{color:black} NAS{color} \|{color:black} Cancelled{color} \| \|{color:black} PI-RLN/2022/0389{color} \|{color:black} 56907{color} \|{color:black} Regular purchase{color} \|{color:black} NULL{color} \|{color:black} NAS{color} \|{color:black} Cancelled{color} \| \|{color:black} PI-RLN/2022/0396{color} \|{color:black} 57265{color} \|{color:black} Regular purchase{color} \|{color:black} NULL{color} \|{color:black} NAS{color} \|{color:black} Cancelled{color} \| \|{color:black} SI-RTN/2022/0131{color} \|{color:black} 57945{color} \|{color:black} NULL{color} \|{color:black} Registered sale{color} \|{color:black} NAS{color} \|{color:black} should be on 101662/0029/0001{color} \| \|{color:black} SI-RTN/2023/0216{color} \|{color:black} 92252{color} \|{color:black} NULL{color} \|{color:black} Registered sale{color} \|{color:black} NAS{color} \|{color:black} should be on 100893/0012/0001{color} \| \|{color:black} PI-RLN/2023/0402{color} \|{color:black} 107876{color} \|{color:black} Regular purchase{color} \|{color:black} NULL{color} \|{color:black} NAS{color} \|{color:black} is posted today on fictive customer with round number{color} \| \|{color:black} PI-RLN/2023/0403{color} \|{color:black} 107877{color} \|{color:black} Regular purchase{color} \|{color:black} NULL{color} \|{color:black} NAS{color} \|{color:black} is posted today on round number 102079/0061/0001{color} \| {color:black}{color} {color:black}The cancelled ones should be disregard.{color} {color:black}Conversion post => Conversiepost.{color} [{color:black}@Bovene\', \'Comment 36: Mitch van{color}\|mailto:[email protected]]{color:black} is it correct that these are posted as regulars?{color} {color:black}{color} {color:black}Could you/or someone change my highlighted yellow 2 lines? It should be on the round mentioned in column remark.{color} {color:black}Thanks!{color} {color:black}{color} \| \|{color:#000001} Metvriendelijkegroet,{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:#000001}{color} \| \| \| \|{color:#000001} Christinede{color} \|{color:#000001} {color} \|{color:#000001} Jong{color} \| {color:#000001}MedewerkerContractadministratie{color} \| \| \|{color:black}{color} {color:black}{color}{color:windowtext}{color}{color:black}{color}!image001!{color:black} <[https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.de-heus.nl%2F&data=05%7C01%7Cmbovene%40deheus.com%7C84169882cda04349420008db2a0c2369%7C1004261bdfb74f37830f7438cb8a1b69%7C1%7C0%7C638150003838789815%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=55URh6sW8pQZOoZoQ3iYubesdl259DyS4eVG7YoMk5o%3D&reserved=0]>{color} \| \| {color:#006FB7} DEHEUSVOEDERSB.V.{color} \| \| \| \|{color:#000001} Postbus396 6710BJEde \\\\u200b{color} \| \|{color:#000001} Rubensstraat175 6717VEEde \\\\u200b{color} \| \| \|{color:#000001} T:0318675567{color} \| {color:#000001}KvK14626985{color} _{color:#000001} _Opdite‑mailberichteneventuelebijlage(n)isdedisclaimervantoepassing_ _gepubliceerdopdewebsitevan_ {color}[{color:#000001}{color}{color:#000001} _+ DeHeusVoeders+_{color}{color:#000001} {color}\|https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.de-heus.nl%2Fprivacy-beleid&data=05%7C01%7Cmbovene%40deheus.com%7C84169882cda04349420008db2a0c2369%7C1004261bdfb74f37830f7438cb8a1b69%7C1%7C0%7C638150003838789815%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=vDpzDgWUEyp4135EutBLC3zkle0sHatFHwLsb6f2aLc%3D&reserved=0]{color:#000001} _._{color}_ \| \| !image002! <[https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.facebook.com%2Fdeheusvoeders&data=05%7C01%7Cmbovene%40deheus.com%7C84169882cda04349420008db2a0c2369%7C1004261bdfb74f37830f7438cb8a1b69%7C1%7C0%7C638150003838946033%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=be2kCHcd3v8xGzO%2BuMvFn0LMQCMvpbGOlkpEJDpA%2B6c%3D&reserved=0]>{color:black}{color} \| \| !image003! <[https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Ftwitter.com%2Fde_heus_voeders&data=05%7C01%7Cmbovene%40deheus.com%7C84169882cda04349420008db2a0c2369%7C1004261bdfb74f37830f7438cb8a1b69%7C1%7C0%7C638150003838946033%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=f8GWbU8bOLYlY2fMVE8OG6GK4ODNihK7XbUoCf%2F5ZRE%3D&reserved=0]>{color:black}{color} \| \| !image004! <[https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.youtube.com%2Fchannel%2FUCqkrGebUlFowgumurz-abxQ&data=05%7C01%7Cmbovene%40deheus.com%7C84169882cda04349420008db2a0c2369%7C1004261bdfb74f37830f7438cb8a1b69%7C1%7C0%7C638150003838946033%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=u%2FyfPAOoVaGFvamj7lztslmOQfnixblyXcE4%2Fq5yv58%3D&reserved=0]>{color:black}{color} \| \| !image005! <[https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.linkedin.com%2Fcompany%2Fde-heus-voeders-b-v-%2F&data=05%7C01%7Cmbovene%40deheus.com%7C84169882cda04349420008db2a0c2369%7C1004261bdfb74f37830f7438cb8a1b69%7C1%7C0%7C638150003838946033%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=%2B5SBRV1Uv9A2hizJiwA%2BzSjb%2FCHL4%2FLZYIeAIn%2FiYnQ%3D&reserved=0]>{color:black}{color} \| Van: Jong\', \'Comment 37: Christine de Verzonden: dinsdag 21 maart 2023 13:41 Aan: [[email protected]\|mailto:[email protected]] Onderwerp: RE: DGS-8722 Round number selection should be obligatory {color:black}Please only make it obligatory in NAS.{color} {color:black}MAS has exceptions.{color} {color:black}{color} {color:black}This csv mostly shows MAS documents.{color} {color:black}I will change the NAS if not already done.{color} {color:black}{color} {color:black}{color} {color:black}{color} {color:black}{color} \| \|{color:#000001} Metvriendelijkegroet,{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:#000001}{color} \| \| \| \|{color:#000001} Christinede{color} \|{color:#000001} {color} \|{color:#000001} Jong{color} \| {color:#000001}MedewerkerContractadministratie{color} \| \| \|{color:black}{color} {color:black}{color}{color:windowtext}{color}{color:black}{color}!image001!{color:black} <[https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.de-heus.nl%2F&data=05%7C01%7Cmbovene%40deheus.com%7C84169882cda04349420008db2a0c2369%7C1004261bdfb74f37830f7438cb8a1b69%7C1%7C0%7C638150003838946033%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=f4LhGvowIfaFCum%2Blou5d6VTxZNN8NQg%2BqfkFOrWnjo%3D&reserved=0]>{color} \| \| {color:#006FB7} DEHEUSVOEDERSB.V.{color} \| \| \| \|{color:#000001} Postbus396 6710BJEde \\\\u200b{color} \| \|{color:#000001} Rubensstraat175 6717VEEde \\\\u200b{color} \| \| \|{color:#000001} T:0318675567{color} \| {color:#000001}KvK14626985{color} _{color:#000001} _Opdite‑mailberichteneventuelebijlage(n)isdedisclaimervantoepassing_ _gepubliceerdopdewebsitevan_ {color}[{color:#000001}{color}{color:#000001} _+ DeHeusVoeders+_{color}{color:#000001} {color}\|https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.de-heus.nl%2Fprivacy-beleid&data=05%7C01%7Cmbovene%40deheus.com%7C84169882cda04349420008db2a0c2369%7C1004261bdfb74f37830f7438cb8a1b69%7C1%7C0%7C638150003838946033%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=Q713OKBUL6iLEHUTIJf1i4%2FdY83qjcStAWJ76SBXn%2Bk%3D&reserved=0]{color:#000001} _._{color}_ \| \| !image002! <[https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.facebook.com%2Fdeheusvoeders&data=05%7C01%7Cmbovene%40deheus.com%7C84169882cda04349420008db2a0c2369%7C1004261bdfb74f37830f7438cb8a1b69%7C1%7C0%7C638150003838946033%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=be2kCHcd3v8xGzO%2BuMvFn0LMQCMvpbGOlkpEJDpA%2B6c%3D&reserved=0]>{color:black}{color} \| \| !image003! <[https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Ftwitter.com%2Fde_heus_voeders&data=05%7C01%7Cmbovene%40deheus.com%7C84169882cda04349420008db2a0c2369%7C1004261bdfb74f37830f7438cb8a1b69%7C1%7C0%7C638150003838946033%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=f8GWbU8bOLYlY2fMVE8OG6GK4ODNihK7XbUoCf%2F5ZRE%3D&reserved=0]>{color:black}{color} \| \| !image004! <[https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.youtube.com%2Fchannel%2FUCqkrGebUlFowgumurz-abxQ&data=05%7C01%7Cmbovene%40deheus.com%7C84169882cda04349420008db2a0c2369%7C1004261bdfb74f37830f7438cb8a1b69%7C1%7C0%7C638150003838946033%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=u%2FyfPAOoVaGFvamj7lztslmOQfnixblyXcE4%2Fq5yv58%3D&reserved=0]>{color:black}{color} \| \| !image005! <[https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.linkedin.com%2Fcompany%2Fde-heus-voeders-b-v-%2F&data=05%7C01%7Cmbovene%40deheus.com%7C84169882cda04349420008db2a0c2369%7C1004261bdfb74f37830f7438cb8a1b69%7C1%7C0%7C638150003838946033%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=%2B5SBRV1Uv9A2hizJiwA%2BzSjb%2FCHL4%2FLZYIeAIn%2FiYnQ%3D&reserved=0]>{color:black}{color} \| Van: Tomasz Zygoń (Jira) <[[email protected]\|mailto:[email protected]]> Verzonden: dinsdag 21 maart 2023 13:26 Aan: Jong\', "Comment 38: Christine de <[[email protected]\|mailto:[email protected]]> Onderwerp: DGS-8722 Round number selection should be obligatory !image006.gif!\'", \'Comment 39: "{color:#000000}Ok\', \'Comment 40: so the final condition for validation in NAS sector is:{color} * {color:#000000}SI/PI should has \\\'Full number\\\' if type of SI/PI = \\\'Regular\\\' or \\\'Registered\\\'{color}"\', "Comment 41: \'{color:black}Yes! That’s correct{color} {color:black}😊{color}{color:black}{color} {color:black}{color} \| \|{color:#000001} Metvriendelijkegroet,{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:#000001}{color} \| \| \| \|{color:#000001} Christinede{color} \|{color:#000001} {color} \|{color:#000001} Jong{color} \| {color:#000001}MedewerkerContractadministratie{color} \| \| \|{color:black}{color} {color:black}{color}{color:windowtext}{color}{color:black}{color}!image001!{color:black} <[https://www.de-heus.nl/]>{color} \| \| {color:#006FB7} DEHEUSVOEDERSB.V.{color} \| \| \| \|{color:#000001} Postbus396 6710BJEde \\\\u200b{color} \| \|{color:#000001} Rubensstraat175 6717VEEde \\\\u200b{color} \| \| \|{color:#000001} T:0318675567{color} \| {color:#000001}KvK14626985{color} _{color:#000001} _Opdite‑mailberichteneventuelebijlage(n)isdedisclaimervantoepassing_ _gepubliceerdopdewebsitevan_ {color}[{color:#000001}{color}{color:#000001} _+ DeHeusVoeders+_{color}{color:#000001} {color}\|https://www.de-heus.nl/privacy-beleid]{color:#000001} _._{color}_ \| \| !image002! <[https://www.facebook.com/deheusvoeders]>{color:black}{color} \| \| !image003! <[https://twitter.com/de_heus_voeders]>{color:black}{color} \| \| !image004! <[https://www.youtube.com/channel/UCqkrGebUlFowgumurz-abxQ]>{color:black}{color} \| \| !image005! <[https://www.linkedin.com/company/de-heus-voeders-b-v-/]>{color:black}{color} \| Van: Damian Świstek (Jira) <[email protected]> Verzonden: dinsdag 21 maart 2023 14:15 Aan: Jong", "Comment 42: Christine de <[email protected]> Onderwerp: DGS-8722 Round number selection should be obligatory \'", \'Comment 43: "Here is a report with invoices with empty rounds:PI,SI without rounds-2.csvCould you please add the customer\', "Comment 44: supplier and reference as columns to this list? I notice that in MAS NL many SI\'s with missing full numbers are related to SR\'s for Belgium customers. And indeed", \'Comment 45: for these customers there are no rounds available in MAS NL."\', "Comment 46: \'{color:black}Hi Mitch,{color} {color:black}{color} {color:black}Already did this for NAS yesterday.{color} {color:black}For MAS I lack the time. If there can be made a selection with customer number/name I can have a look.{color} {color:black}{color} \| \|{color:#000001} Metvriendelijkegroet,{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:#000001}{color} \| \| \| \|{color:#000001} Christinede{color} \|{color:#000001} {color} \|{color:#000001} Jong{color} \| {color:#000001}MedewerkerContractadministratie{color} \| \| \|{color:windowtext}{color} !image001! <[https://www.de-heus.nl/]>{color:black}{color} \| \| {color:#006FB7} DEHEUSVOEDERSB.V.{color} \| \| \| \|{color:#000001} Postbus396 6710BJEde \\\\u200b{color} \| \|{color:#000001} Rubensstraat175 6717VEEde \\\\u200b{color} \| \| \|{color:#000001} T:0318675567{color} \| {color:#000001}KvK14626985{color} _{color:#000001} _Opdite‑mailberichteneventuelebijlage(n)isdedisclaimervantoepassing_ _gepubliceerdopdewebsitevan_{color}_[ _{color:#000001} _DeHeusVoeders_{color}_\|https://www.de-heus.nl/privacy-beleid] _{color:#000001} _._{color}_ \| \| !image002! <[https://www.facebook.com/deheusvoeders]>{color:black}{color} \| \| !image003! <[https://twitter.com/de_heus_voeders]>{color:black}{color} \| \| !image004! <[https://www.youtube.com/channel/UCqkrGebUlFowgumurz-abxQ]>{color:black}{color} \| \| !image005! <[https://www.linkedin.com/company/de-heus-voeders-b-v-/]>{color:black}{color} \| Van: Mitch van Bovene (Jira) <[email protected]> Verzonden: dinsdag 21 maart 2023 15:59 Aan: Jong", "Comment 47: Christine de <[email protected]> Onderwerp: DGS-8722 Round number selection should be obligatory \'", "Comment 48: \'Here is report with PI,SI without rounds with Customer", \'Comment 49: Reference\', "Comment 50: Supplier columns[^PI,SI without rounds.xlsx]\']"]\nRelated Issues:\n[]\n\n### End'}
311	{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8721\n\n### Instruction:\nPO 157/23 created in February is not showing in Johnson DHP\n\n### Response:\n["Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", "Comment 2: \'I do not see the linking of this item 960917", "Comment 3: !screenshot-1! Can you check?\'", "Comment 4: \'you are right. i will work on the linking. please close\']"]\nRelated Issues:\n[]\n\n### End'}
312	{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8720\n\n### Instruction:\nIn DHP, the rewok icon does not appear for this item. The recipe is available at DHC.\r\n\r\nCan you chek please?\n\n### Response:\n["Comment 1: [\'!image!\'", "Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", "Comment 3: \'!image-2023-03-09-14-51-43-839.png!\'", \'Comment 4: "{code:java}SELECT * FROM [DHPlantProdBusinessLogicMain].[dbo].[Items] where code = \\\'31640140-B20\\\' or id = \\\'77DDCF8C-C538-4537-A0EF-1808AC8717F8\\\'SELECT * FROM [DHPlantProdBusinessLogicMain].[dbo].[ProductionLots] where LotNumber = 0371080323005 select * from [DHPlantProdBusinessLogicMain].[dbo].[ProductionLotElements] where --RecipeId = \\\'AECC782F-D3F8-45BD-83D5-96A8DABA553B\\\' ItemId in ( \\\'77DDCF8C-C538-4537-A0EF-1808AC8717F8\\\',\\\'7A82B2B7-0B5C-497A-9F2E-DBD5F6BC5CAC\\\'){code}"\', "Comment 5: \'Warunki dla Broken Batcha!image-2023-03-10-08-07-51-818.png!W DHC brakuje additional technology dla tego itema!image-2023-03-10-08-06-46-398.png!!image-2023-03-10-08-10-11-348.png!!image-2023-03-10-08-10-11-348!\'", "Comment 6: \'!image-2023-03-10-08-13-36-241.png!\'", "Comment 7: \'Please", \'Comment 8: verify\', "Comment 9: the item is not the sameRegards!image-2023-03-10-08-24-19-177.png!!image-2023-03-10-08-41-10-206.png!\'", "Comment 10: \'[[DHP] Cannot create rework\|onenote:https://kotrak.sharepoint.com/sites/erpasysta/Shared%20Documents/Baza%20wiedzy/Baza%20Wiedzy%20-%20ERPSD/Klienci/DEHEUS/DEHEUS%20APPLICATIONS/Serbia/Baza%20wiedzy.one#%5bDHP%5d%20Cannot%20create%20rework&section-id=\\\\\\\\{2D7CB55A-B2DD-4CFE-B5DC-732963C5C855}&page-id=\\\\\\\\{DA51F7E9-38C9-44AA-BFA1-C92D0B5BCD86}&end] ([Widok sieci Web\|https://kotrak.sharepoint.com/sites/erpasysta/_layouts/OneNote.aspx?id=%2Fsites%2Ferpasysta%2FShared%20Documents%2FBaza%20wiedzy%2FBaza%20Wiedzy%20-%20ERPSD&wd=target%28Klienci%2FDEHEUS%2FDEHEUS%20APPLICATIONS%2FSerbia%2FBaza%20wiedzy.one%7C2D7CB55A-B2DD-4CFE-B5DC-732963C5C855%2F%5BDHP%5D%20Cannot%20create%20rework%7CDA51F7E9-38C9-44AA-BFA1-C92D0B5BCD86%2F%29])\'", "Comment 11: \'Hi,Can we close this task?Regards\'", "Comment 12: \'Hello,We are closing this task as we haven’treceivedany replyfromyouforalong time. If the issueappearsagain", "Comment 13: please raise another task.Regards\']"]\nRelated Issues:\n[]\n\n### End'}
313	{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8719\n\n### Instruction:\nSOR-45/02/2023 : Change main/target to customer Coops to KR000000029\n\n### Response:\n["Comment 1: [\'!image!\'", "Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", "Comment 3: \'Changed. Please", "Comment 4: verify.Regards!image-2023-03-09-11-35-02-285.png!!image-2023-03-09-11-35-17-434.png!\'", "Comment 5: \'User did have an comment.They mentioned also an sales invoice.I have asked them to specify what is wanted,\'", "Comment 6: \'I did have an reponce.Please do the same with : si-55.02.2023.V \'", "Comment 7: \'Initially only SOR was requested.I have changed customer data on Invoice. Please", "Comment 8: verify!image-2023-03-17-09-33-14-933.png!Regards\'", "Comment 9: \'Ticket can be closed\']"]\nRelated Issues:\n[]\n\n### End'}
314	{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8718\n\n### Instruction:\nWe have problem with generating documents shipment.\r\nDatabase sql05-20\\upg \r\n\n\n### Response:\n["Comment 1: [\'!image!!image-1!\'", \'Comment 2: "Hi Edyta\', \'Comment 3: please create issue in DHITS project because it\\\'s a problem with the test environment."\', "Comment 4: \'Hi Piotr", "Comment 5: Thank you for information. You can close this task.\']"]\nRelated Issues:\n[]\n\n### End'}
315	{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8717\n\n### Instruction:\nI tried to add/change conditions for a contract in MAS NL. I couldn\'t select a receiver, because it was hard coded on \'according to defined\'. Next, the contract was sent back to \'Administrator\' for changing the conditions. This inbox, I can\'t reach. Could you make sure that the person who does this handling in MAS NL is the one who receives the contract for modifying?\n\n### Response:\n["Comment 1: [\'!image!\'", \'Comment 2: "Hello Steffen,Flow Add change conditions send documents to user who create this document and this is how it\\\'s configured right now. This CF comes from import\', \'Comment 3: so document went to Administrator\\\'s inbox because all documents from import have been created by Administrator.Should we send this documentCF-M/0040 to \\\'Waiting for approval\\\' to Bessel\\\'s inbox?Is there needed to make any changes in this flow Add/change conditions?!image-2023-03-09-09-28-39-507.png!!image-2023-03-09-09-26-39-405.png!"\', \'Comment 4: "Hello Damian,Yes\', "Comment 5: we can see Bessel\'s inbox so that would be an option. Administrator we can\'t and we couldn\'t manually send it to Bessel\'s inbox. I know that there is a totally different flow in MAS BE", "Comment 6: but I don\'t know if we could and should do this in MAS NL. We only need to be able to modify contracts from some inbox", \'Comment 7: so this will happen more often."\', \'Comment 8: "I\\\'ve sentCF-M/0040 document to Bessel\\\'s inbox\', \'Comment 9: so I hope you can sent it to next flows and edit document. If not\', \'Comment 10: please let us know.Maybe we should think about some adjustments in process it it will be more cases like this.We can adjust it similar like in MAS BE - there is a role for it and document is sent to few users insted of one who created document.@Mitch do you think that it should be adjusted somehow in MAS NL?"\', "Comment 11: \'So in the future all documents will go to the original creator?I am not sure how we want this to work. If it can be send to the head of the department it will be fine.\'", \'Comment 12: "The problem is that the contract goes automatically to administrator once we click \\\'add/change conditions\\\'. So everytime we do this the contract will go to administrator. I can\\\'t choose Bessel or myself or anyone else. Therefor in MAS BE there is a whole other flow for this process."\', \'Comment 13: "{quote}So in the future all documents will go to the original creator?{quote}Yes\', "Comment 14: documents will go to the user who will create document. Now there are a lot of contracts from migration which we created as Administrator and flow sends these contracts to Administrator.At this moment it looks like that in MAS NL for Contract farmer documents. Everytime when someone will choose\'add/change conditions\' document will go to this user who created CF.!image-2023-03-09-13-38-28-527.png!{quote}I am not sure how we want this to work. If it can be send to the head of the department it will be fine.{quote}We can add some role or use existing (Senior contract administrator role is connected with state\'add/change conditions\') with users and then user can choose who should get this CF whenclick \'add/change conditions\'", \'Comment 15: we need only list of users possible to select in this flow if it should be handle in that way."\', \'Comment 16: "Let\\\'s do it like that. Who needs to be in this option menu:MAS NL - Nancy\', \'Comment 17: Koen & Peter MAS BE - Koen & SteffenNAS - Christine & BertVAS - Bert & PeterPAS/OPPAS - Thelma & PeterLAS - Bert & Peter"\', "Comment 18: \'Hello,I have 2 questions:1. What is the status of this? I have a few contracts I need to open and modify in MAS NL2. Is it possible that I will be added to the MAS NL list? (I discussed this with Koen)\'", "Comment 19: \'Update:The one you put in Bessel\\\\\'s inbox I modified and then approved the change. Now that it\\\\\'s active again", \'Comment 20: the contract goes back to "Administrator".!image-1!\\\'\', \'Comment 21: "Hi Steffen,We can add you also to this list in MAS NL for flow \\\'Add/change conditions\\\'.How we should handle it with flow \\\'Active (revised)\\\' - should we adjust it sismilar like in the flow\\\'Add/change conditions\\\'?What should we do with these document. We can send some documents to Add change conditions before changes if it\\\'s urgent and you need to work with these documents. Please let us know which documents should be possible to adjust by you or other users (In MAS NLNancy\', \'Comment 22: Koen\', \'Comment 23: Peter\', \'Comment 24: Steffen)Regards"\', \'Comment 25: "I would indeed think that this named flow is sufficient for contract farmer\', \'Comment 26: so both for add/changing conditions\', \'Comment 27: approval and activation. Other documents like invoices\', \'Comment 28: rounds and feed sales we can re-open through \\\'start new proces\\\'."\', "Comment 29: \'Is there already an update on this? I should need to edit some contracts this week in MAS NL.\'", "Comment 30: \'Hello,What is the status of this topic?\'", \'Comment 31: "Hello,We\\\'re working on this topic and it should be ready on test environment today.We\\\'ll inform you in task when it will be ready to test.Regards"\', "Comment 32: \'You can test it now on UAT.\'", "Comment 33: \'Hello,The flow to add/change conditions is fine.However", \'Comment 34: when approving the changes (as specialist and as sector lead)\', "Comment 35: can we be selected there as well?Now the contract will only still be in my inbox afterwards if I put myself as specialist and sector lead. !image-2!!image-3!\'", "Comment 36: \'I fix it", "Comment 37: You can test it again.\'", \'Comment 38: "I don\\\'t see it yet for starting the approval flow (screenshot 1)\', \'Comment 39: the first approval (screenshot 2) but I do for the last approval (screenshot 3). So if you can add those lists on screenshot 3 for phase 1 and 2 it will be perfect.!image-4!!image-5!!image-6!"\', \'Comment 40: "[[email protected]][[email protected]]In MAS NL sector when someone sent document to \\\'Waiting for approval\\\' state\', \'Comment 41: system everytime sent it to user from Document field \\\'Specialist\\\' or \\\'Sector lead\\\' (on screen below there are 3 flows with waiting for approval).It works from the beginning of the system like that.Please let us know that we indeed should change this flow/flows in MAS NL. Maybe you refer only to flow from \\\'Add/change conditions\\\' to \\\'Waiting for approval\\\' and here we should make changes and do it similar like for \\\'Add/change condition\\\' flow?!image-2023-03-27-11-35-55-947.png!"\', \'Comment 42: "I think in MAS BE\', \'Comment 43: we select ourselves as specialist and sector lead when making the contract\', "Comment 44: so we can approve it ourselves (you can\'t choose anyone else). Afterwards", \'Comment 45: we add/change the conditions where we can send that task to ourselves\', \'Comment 46: and then we modify the sector lead and specialist to the correct persons\', \'Comment 47: because we ourselves can do the whole flow."\', "Comment 48: \'Damian", \'Comment 49: to make it even more dynamic within De Heus they decided that the specialist and sector lead doesn\\\\\\\'t have to approve the contracts any more (at least in the Intense system).This means that the contract approval flow can be changed. The user must be able to manually select someone in the system to approve the contract. It can be reduced to one step (Draft - waiting for approval - approved --> active). It should not be send automatically to the persons that are set in Specialist and Sector lead fields.A similar process holds for the "add/change conditions" approval flow.Is this clear?\\\'\', "Comment 50: \'Note: for all sectors.\'", \'Comment 51: "Does it means we don\\\'t need to use anymore approval flows in all sectors for Contract Farmer documents?How it is: # Regular process: Draft -> Waiting for approval -> Approved by specialist -> Active # Aadd/change conditions process: Active -> Add/change conditions -> Waiting for approval -> Approved by specialist -> Active (revised)To whom should be possible to sent document to Active? It should be users from role with this sector (all users from sector) or from other role/users?(Now when document is sent to Active is sent to user who create CF document).How it should be: # Regular process: Draft -> Active # Aadd/change conditions process: Active ->Add/change conditions -> Active (revised)To whom should be possible to sent document from Add/change conditions to Active? It should be users from role with this sector (all users from sector) or from other role/users?(Now when document is sent to Active is sent to user who create CF document).Could you confirm/add some remarks?"\', \'Comment 52: "Does it means we don\\\'t need to use anymore approval flows in all sectors for Contract Farmer documents? --> NOBut now we have two steps: approved by specialst and approved by sector lead.The flow is guided automatically by the system.We would like to have one approval step\', \'Comment 53: and the user should be able to manually select the user to send the document to."\', "Comment 54: \'To whom should be possible to sent document from Add/change conditions to Active? --> user should be able to select a collegue from their departmentIt should be users from role with this sector (all users from sector) or from other role/users? --> Contract administrator or Senior Contract administrator.\'", \'Comment 55: "Proces dla dokumentów CF we wszystkich sektorach powinien wyglądać tak:Standardowy proces:Draft -> Waiting for Approval -> ActivePrzy wysyłce do węzła \\\'Waiting for Approval\\\' powinno dać się wybrać jednego użytkownika\', \'Comment 56: do którego zostanie wysłany dokument - w zależności od sektora powinna tu być dostępna lista użytkowników\', "Comment 57: którzy mają dostęp do danego sektora.Do dodania przepływ:Waiting for Approval -> ActiveProces ze zmianami w CF (Add/change conditions):Active -> Add/change conditions -> Active (revised)Przy wysyłce z węzła\'Add/change conditions\' do\'Active (revised)\' powinna być dostępna lista użytkowników", \'Comment 58: którzy są w rolachContract administrator i Senior Contract administrator.Do dodania przepływ:Add/change conditions -> Active (revised)------Pozostałe przepływy akceptacyjne\', \'Comment 59: które były do tej pory używane powinny być niedostępne.Należy pamiętać\', \'Comment 60: że jeżeli są dokumenty w węzłach biorących udział w starych procesach\', \'Comment 61: to należałoby zakończyć takie procesy zanim zmiana zostanie wprowadzona\', \'Comment 62: w innym wypadku może się okazać\', \'Comment 63: że niektórych dokumentów nie będzie się dało przeprocesować do końca."\', "Comment 64: \'Ok", "Comment 65: then processes will be: # Regular process:Draft -> Waiting for Approval -> Active # Add/change conditions process:Active -> Add/change conditions -> Active (revised)\'", "Comment 66: \'YES\'", "Comment 67: \'Created flows on the test environment according to guidelines\'", "Comment 68: \'I tested both and according to me both flows are good", "Comment 69: but maybe Mitch can have a look as well to confirm.\'", \'Comment 70: \\\'Regular process (first picture): Draft -> Waiting for Approval -> ActiveThis works fine. However I am wondering why the approver needs to select another person in order to activate it. Will it be send to the inbox o the person in that selection?Add/change conditions process:Active -> Add/change conditions -> Active (revised)To whom is this contract send when I select "Add/change conditions"? I cannot make any selection\', \'Comment 71: it is send according to the definition (second picture). The same holds for the person who is receiving this contract in the status "Add/change conditions" state. I can\\\\\\\'t manually select who I would like to send this document to.!image-7!!image-8!\\\'\', \'Comment 72: \\\'Mitch,Regarding this: "To whom is this contract send when I select "Add/change conditions"? I cannot make any selection\', \'Comment 73: it is send according to the definition (second picture). The same holds for the person who is receiving this contract in the status "Add/change conditions" state. I can\\\\\\\'t manually select who I would like to send this document to." --> In MAS BE\', "Comment 74: I could select Koen or myself there.\'", "Comment 75: \'[[email protected]]możesz to sprawdzić i odpowiedzieć na ostatnie komentarze?\'", "Comment 76: \'{quote}Regular process (first picture):Draft -> Waiting for Approval -> ActiveThis works fine. However I am wondering why the approver needs to select another person in order to activate it. Will it be send to the inbox o the person in that selection?{quote}Exactly", \'Comment 77: document will be send to to inbox of user which you select (insted of user who created document).{quote}Mitch,Regarding this: "To whom is this contract send when I select "Add/change conditions"? I cannot make any selection\', \'Comment 78: it is send according to the definition (second picture). The same holds for the person who is receiving this contract in the status "Add/change conditions" state. I can\\\\\\\'t manually select who I would like to send this document to." --> In MAS BE\', \'Comment 79: I could select Koen or myself there.{quote}Yes\', "Comment 80: on test environment there is a list in each sector with users to whom will be sended document. Maybe you tried to do on Prod environment - it\\\\\'s not adjusted there yet.If process on test environment works properly we can move it to Production environment.Please confirm if we can move this to Prod.\'", "Comment 81: \'Hello Damian,I personally think it can be moved to PROD. For what I tested it", "Comment 82: it worked.\'", "Comment 83: \'Moved to production\'", "Comment 84: \'Can be closed\']"]\nRelated Issues:\n[]\n\n### End'}
316	{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8716\n\n### Instruction:\nBecause all items are send to all sectors right now (after the latest Intense update) we don\'t need the field "Multisector" anymore.\r\n\r\nCould this field be hidden?\n\n### Response:\n["Comment 1: [\'!image-1!\'", \'Comment 2: "After change only Items sent from Milas with Item Group = \\\'Finish Product\\\' or \\\'Raw Materials\\\' are directly created as a Item Card and sent to all sectors\', \'Comment 3: but other items are sent as a New Item Card\', "Comment 4: so I think this functionality with Multisector can be used for this cases when Item Group is different than\'Finish Product\' or \'Raw Materials\'.We can hide this if you\'re sure there won\'t be cases with items sent from Milas which are not needed to create in many sectors.For example there is some\'New Item Card\' in MAS NL sector right now on IBIP_DH and here are selected 5 sectors", \'Comment 5: so it won\\\'t be possible in the future when we hide this option on New Item Card.Should we indeed hide this option from New Item Card?!image-2023-03-09-09-57-44-874.png!"\', \'Comment 6: "You are right. For items that are not in the \\\'Finish Product\\\' or \\\'Raw Materials\\\' item groups we indeed need this functionality.It is an option to hide it when it is in the \\\'Finish Product\\\' or \\\'Raw Materials\\\' item groups?"\', "Comment 7: \'Ok", "Comment 8: we will hide this fields as you wrote.\'", "Comment 9: \'Can be closed when this field is hidden.\'", "Comment 10: \'Can be closed\']"]\nRelated Issues:\n[]\n\n### End'}
317	{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8715\n\n### Instruction:\nWe have error in the VT-1342/23, item SUE1605-S25, we have reservation WD-919/3/23, we cancelled because quantity was wrong, but after cancel the item is reserved yet.\r\nCould you please remove reservation, it\'s urgent remove reservation, truck is waiting to load.\r\n\r\nThank you\n\n### Response:\n["Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", \'Comment 2: "HelloAs you can see by yourself in the query bellow\', \'Comment 3: we have around 50 UL with executed documents stuck on SU reservation:{noformat} SELECT \\\\tul.Barcode\', \'Comment 4: su.ReservedQuantityValue\', \'Comment 5: su.ReservedQuantityUnit\', \'Comment 6: su.ReservationSourceDocumentNumbers\', \'Comment 7: wd.Status FROM DHPlantWmsBusinessLogicMain.dbo.UnitLoads ul \\\\tINNER JOIN DHPlantWmsBusinessLogicMain.dbo.StockUnits su ON su.UnitLoadId = ul.Id \\\\tINNER JOIN DHPlantWmsBusinessLogicMain.dbo.WarehouseDispatches wd ON wd.Document = REPLACE(TRIM(su.ReservationSourceDocumentNumbers)\', "Comment 8: \';\'", \'Comment 9: \\\'\\\')WHERE su.ReservationSourceDocumentNumbers LIKE \\\'%WD%\\\'{noformat}Could you please fix that?Thank you"\', "Comment 10: \'Hello", \'Comment 11: only WD-886/3/23 has status=60.I corrected this one.For the rest\', "Comment 12: the documents are still in progress:WO(PD)-98/3/23,WO(PD)-156/3/23.Please check after completion.\'", \'Comment 13: "{code:java}declare @barcode nvarchar(max) = \\\'89-W0088A\\\'delete sr--select from dbo.StockUnits sinner join dbo.StockUnitReservations sr on sr.Id = s.Idwhere s.Barcode = @barcodeupdate dbo.StockUNITSSET QuantityOnhand = Quantitywhere barcode = @barcodeupdate suset su.QuantityOnHandValue=880,su.ReservedQuantityValue=0,su.ReservationSourceDocumentNumbers=\\\'\\\' --select su.QuantityOnHandValue,su.ReservedQuantityValue,su.ReservationSourceDocumentNumbers, FROM [DHPlantWmsBusinessLogicMain].[dbo].[UnitLoads] ul inner join [DHPlantWmsBusinessLogicMain].dbo.StockUnits su on ul.id=su.UnitLoadId where ul.Barcode=@barcode{code}"\', \'Comment 14: "Analizując ostatni przykład to w stock dla tego stockunit jest rezerwacja jako ostatnia{code:java}SELECT [Event],[StoredAt] ,[EventType] ,[UserName] ,[CorrelationId] ,[CreatedAt] ,[SentAt] FROM [DHPlantStockBusinessLogicEvents].[dbo].[StockUnits] where AggregateId=\\\'4FFA1A0F-15C4-4BF9-90B3-C5F3B9C3DB9A\\\' order by StoredAt asc{code} !screenshot-2! Sprawdzając WD i anulację - operator rozpoczął dopiero po 18:10\', \'Comment 15: gdzie w stocku nie ma tego ujętego(to wyżej).{code:java}SELECT [Event]\', \'Comment 16: [StoredAt] ,[EventType] ,[UserName] FROM [DHPlantWmsBusinessLogicEvents].[dbo].[WarehouseDispatches] where AggregateId=\\\'D7B488EF-C05E-4B9E-A194-9EC2CCD25CA9\\\' order by StoredAt asc{code} !screenshot-3! "\', "Comment 17: \'zgodnie z rozmową ", "Comment 18: dzięki.\'", "Comment 19: \'Sytuacja analogiczna do przypadku zgłoszonego w DGS-8450: https://helpdesk.kotrak.com/browse/DGS-8450?focusedCommentId=1098904&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-1098904Problem zostanie rozwiązany na GDC-849 ( obsługi konkurencyjności).89-W0088A: O 2023-03-07 17:57:29.3778171 WarehouseDispatchSubElementCreatedEvent -> 89-W0088A został zarezerwowany i zarejestrowany na WO(PD): dbo.WarehouseDispatchSubElements -> Element 2", \'Comment 20: Subelement 540ms później o 2023-03-07 17:57:29.7504353 mamy kolejny event WarehouseDispatchSubElementCreatedEvent na ten sam WD element i subelement\', \'Comment 21: ale z kodem 89-W0086R. Kod zostaje zapisany w tabeli WarehouseDispatchSubElements ( Element 2\', \'Comment 22: Subelement 5)\', \'Comment 23: nadpisując 89-W0088A.Użytkownik usuwa dokument WD. Wszystkie rezerwacje zostały usunięte\', "Comment 24: oprócz 89-W0088A - bo tego kod został nadpisany i nie ma na WD.!89-W0088A_WD element!!89-W0088A_created!\'", "Comment 25: \'The issue will be resolved in the GDC-849 (competitive handling).89-W0088A:At 2023-03-07 17:57:29.3778171 has been reserved and registered on WO(PD).40ms later at 2023-03-07 17:57:29.7504353 we have another WarehouseDispatchSubElementCreatedEvent event for the same WD element and subelement", \'Comment 26: but with code 89-W0086R.The user deletes the WD document. All reservations have been deleted\', "Comment 27: except for 89-W0088A - because this code has been overwritten and is not on WD.\'", "Comment 28: \'Ok", "Comment 29: we are waiting new version.\'", "Comment 30: \'This ticket has been closed.\']"]\nRelated Issues:\n[\'DGS-8712\', \'DGS-8450\', \'DGS-8792\', \'DAP-13479\', \'DGS-8640\', \'DGS-8646\', \'DGS-8785\']\n\n### End'}
318	{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8714\n\n### Instruction:\nWe would like to add a button and 8 fields on the Feed tab in the round. These 8 fields are related to "Beginvoorraad" and "Eindvoorraad". \r\n\r\nWe need two fields per round for each of these (see mockup):\r\no\tBeginvoorraad voer\r\no\tBeginvoorraad tarwe\r\no\tEindvoorraad voer (weights should always be negative)\r\no\tEindvoorraad tarwe (weights should always be negative)\r\n\r\nOn the PDF in the Financial Statement, the 4 completed fields must be put in the right place. When this is done the current calculations that are done can still be made.\r\n\r\nPlease note: these lines may not come back to S2P, they are purely for registration purposes.\n\n### Response:\n["Comment 1: [\'!image-1!!image-2!\'", \'Comment 2: "We can add these 8 fields and like it is on example we should take in the same way these values which are now displayed on FS new printout right?It should works like if somene will use button\', \'Comment 3: system will calculate values from Feed sale document based on BV\', "Comment 4: EV columns and update these 8 new fields on round? Should these fields be not editable for users?Other option is to calculate these values automatically on document - it will be dynamic text instead of field in database and user don\'t need to use button everytime when values on feed sale will change (new lines will be marked as BV or EBV)- like for example this one!image-2023-03-09-11-03-34-163.png!How should be displayed in new fields on round values:{quote}Eindvoorraad voer (weights should always be negative)Eindvoorraad tarwe (weights should always be negative){quote}It doesn\'t matter what sign is on Feed sale line (negative or positive) and it should be always displayed as a negative values?What about the Net Value for \'Eindvoorraad voer\'", "Comment 5: \'Eindvoorraad tarwe\' - these values should be also always displayed as a negative values?Like it\'s on some example below on database there are values on Feed sale with negative values (but it could happen that this will be also positive)", "Comment 6: so that\'s why I\'m asking.To be sure - we distinguish values for Feed and Wheat (tarwe) on printout by the Item Group on Item Card", "Comment 7: so it means: * if Item has Item Group = \'Finished prodcut\' it\'s displayed as a \'Feed\' * if Item has Item Group = \'Raw Materials\' it\'s displayed as a \'Tarwe\'Is it a good approach and we need to calculate also values for this fields like on FS new printout", \'Comment 8: right?!image-2023-03-09-10-42-51-867.png!"\', \'Comment 9: "After our meeting there is a way how it should works:8 fields on Round should be added and should be editable\', \'Comment 10: users will manually add there values:For these 4 fields should be validation and users should be able to add only positive values: * BV feed Weight\', \'Comment 11: * BV feed Net Value\', \'Comment 12: * BV wheat Weight\', \'Comment 13: * BV wheat Net Value.For these 4 fields should be validation and users should be able to add only negative values: * EV feed Weight\', \'Comment 14: * EV feed Net Value\', \'Comment 15: * EV wheat Weight\', \'Comment 16: * EV wheat Net Value.These fields should be copied from old round to new round (when it is created) - EV values from old round should be copied to BV values for new round with opposite signs:\|\|Round 1\|\|Round 2\|\|\|EV feed Weight = -100\|BV feed Weight = 100\|\|EV feed Net Value = -3000\|BV feed Net Value =3000\|\|EV wheat Weight = -50\|BV wheat Weight = 50\|\|EV wheat Net Value = -1500\|BV wheat Net Value = 1500\|All values from this fields should be included in: * FS printout (new) - values should be retrieved straightly from these 8 fields to sections \\\'Beginvoorrad\\\' and \\\'Eindvoorrad\\\' on printout and should be also calculated in subtotal/totals. This values will be filled in only on Round document and it won\\\'t be included on Feed sale document.Values from Feed sales lines will be presented only in section \\\'Voerleveringen\\\' on printout.!image-2023-03-09-12-58-08-594.png! * Technical results - values from these 8 fields should be included in technical results calculations (e.g.Total weight Feed (in kg),Total value Feed) - to analyse which calculations should include also these values."\', "Comment 17: \'You are totally right.\'", "Comment 18: \'What is the status?\'", \'Comment 19: "It\\\'s related also to other tasks and it\\\'s needed to analyse and discuss to do it properly:[https://helpdesk.kotrak.com/servicedesk/customer/portal/56/DGS-8675][https://helpdesk.kotrak.com/servicedesk/customer/portal/56/DGS-8732]"\', \'Comment 20: "[[email protected]]I have a question about including these new 8 fields to some calculations.We only need to include these values to technical results calculations\', "Comment 21: right?I\'m asking because one of parameters from technical results \'Saldo per m2\' based on Saldo from Financial statement", \'Comment 22: so this value shouldn\\\'t change?!image-2023-04-18-14-22-35-768.png!"\', "Comment 23: \'The Saldo should change when we have BV (begin stock) or EV (end stock). These will change the feed costs for a specifc round", \'Comment 24: so it will affect the saldo.So as a result the "Saldo per m2" should also change.\\\'\', "Comment 25: \'[[email protected]]możesz poprawić nowy wydruk FS", "Comment 26: póki co dla MAS NL.Nowe 8 pól powinno być wyświetlanych wprost z dokumentu Rundy zamiast pobierane z Feed sale.Przykładowy dokument na na IBIP_DH_TEST:FS77901Runda30400\'", \'Comment 27: "[[email protected]]but issue is that calculation of \\\'Saldo\\\' field on FS is based on Gross values from invoices and feed sales.On Round we have Net Values of BV and EV\', \'Comment 28: so should we include these net values to gross values from Saldo?We don\\\'t have any information about Gross Value of BV and EV!image-2023-04-19-13-08-40-729.png!!image-2023-04-19-13-07-28-053.png!"\', "Comment 29: \'zmieniona proceduraKR_calculatetechresults", "Comment 30: funkcjaKR_FinancialStatementSaldo oraz nowy wydruk FS (Financial Statement 2) na IBIP_DH_TEST\'", \'Comment 31: "It\\\'s ready to test on Test environment in MAS NL sector.Values from new 8 fields will be on printout and will be included in calculations of technical results.These changes (after filled in these new 8 fields for BV and EV on Round) in technical results calculation will have impact on these parameters:\|Total weight Feed (in kg)\|\|Total value Feed\|\|Feed conversion netto\|\|Feed conversion 1.500 gram\|\|Feed profit per broiler\|\|Average price feed per 100 kg\|\|Feedcost / kg. broilers bruto 1500 gr\|\|Feedcost / kg. broilers netto\|\|Feedcost / kg. broilers netto\|\|Feed use per delivered broiler per gram per day\|\|Percentage Wheat\|\|Saldo per m2\|\|Saldo / m2 / day\|\|Feed Profit / m2 / day\|\|Percentage Corn\|\|Feed profit\|For Financial Statement saldo there is also change of calculating - now there will be calculated net values from invoices and feed sales instead of gross values as it was before. (for now in MAS NL)!image-2023-04-19-15-34-35-707.png!"\', "Comment 32: \'Move to PROD\'", "Comment 33: \'{color:black}Hello{color} {color:black}{color} {color:black}Is this already set to the PROD{color} {color:black}We can’t see this{color} {color:black}{color} \| \|{color:#000001} Metvriendelijkegroet,{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:#000001}{color} \| \| \| \|{color:#000001} Koen{color} \|{color:#000001} {color} \|{color:#000001} Huibers{color} \| {color:#000001}+31318675600{color} \| \| \|{color:black}{color} {color:black}{color}{color:windowtext}{color}{color:black}{color}!image001!{color:black} <[https://www.de-heus.nl/]>{color} \| \| {color:#006FB7} DEHEUSVOEDERSB.V.‑LOCATIEHELMOND{color} \| \| \| \|{color:#000001} Gerstdijk12 \\\\u200b5704RGHelmond{color} \| \| \|{color:#000001} M:{color}{color:#000001}{color}{color:#000001}+32-11-546672{color}{color:#000001} <tel:+32%20-%2011%20-%2054%2066%2072>{color} \| {color:#000001}KvK14626985{color} _{color:#000001} _Opdite‑mailberichteneventuelebijlage(n)isdedisclaimervantoepassing_ _gepubliceerdopdewebsitevan_ {color}[{color:#000001}{color}{color:#000001} _+ DeHeusVoeders+_{color}{color:#000001} {color}\|https://www.de-heus.nl/privacy-beleid]{color:#000001} _._{color}_ \| \| !image002! <[https://www.facebook.com/deheusvoeders]>{color:black}{color} \| \| !image003! <[https://twitter.com/de_heus_voeders]>{color:black}{color} \| \| !image004! <[https://www.youtube.com/channel/UCqkrGebUlFowgumurz-abxQ]>{color:black}{color} \| \| !image005! <[https://www.linkedin.com/company/de-heus-voeders-b-v-/]>{color:black}{color} \| Van: Mitch van Bovene (Jira) <[email protected]> Verzonden: donderdag 20 april 2023 14:32 Aan: Huibers", "Comment 34: Koen <[email protected]> Onderwerp: DGS-8714 Add button for BV & EV on round \'", \'Comment 35: "Hello,We\\\'re moving it right now on PROD enviroment for MAS NL\', \'Comment 36: I\\\'ll let you know when it will be moved.For MAS BE we\\\'re making changes and it should be ready today to test on TEST environment. I\\\'ll let you know."\', \'Comment 37: "MAS NLChanges have been moved to Production environment.MAS BEIt\\\'s ready to test on Test environment in MAS BL sector.Values from new 8 fields will be on printout and will be included in calculations of technical results.These changes (after filled in these new 8 fields for BV and EV on Round) in technical results calculation will have impact on these parameters:\|Total weight Feed (in kg)\|\|Total value Feed\|\|Feed conversion netto\|\|Feed conversion 1.500 gram\|\|Feed profit per broiler\|\|Average price feed per 100 kg\|\|Feedcost / kg. broilers bruto 1500 gr\|\|Feedcost / kg. broilers netto\|\|Feedcost / kg. broilers netto\|\|Feed use per delivered broiler per gram per day\|\|Percentage Wheat\|\|Saldo per m2\|\|Saldo / m2 / day\|\|Feed Profit / m2 / day\|\|Percentage Corn\|\|Feed profit\|For Financial Statement saldo there is also change of calculating - now there will be calculated net values from invoices and feed sales instead of gross values as it was before. (for now in MAS BE)"\', "Comment 38: \'[15:59] Driesens", \'Comment 39: SteffenBV/EV fields and calculations in MAS BE test works\', "Comment 40: so may be moved to PROD\'", "Comment 41: \'[[email protected]]przeniesiesz na prod to dla MAS BE?\'", \'Comment 42: "Hi,we\\\'ve moved all functionality for MAS BE to PROD Intense environment. You can feel free to test it.Best regards\', \'Comment 43: Grzegorz"\', "Comment 44: \'Zmiany dokonane zostały dla: - dokumentu Roundy", \'Comment 45: dodanie pól na formularzu\', \'Comment 46: - zmiany procedury wydruku FS new\', \'Comment 47: - zmiany procedury saldo na FS\', "Comment 48: - zmiany procedury kalkulacji FS.\']"]\nRelated Issues:\n[\'DGS-8215\', \'DGS-8732\', \'DGS-8877\', \'DGS-8994\']\n\n### End'}
319	{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8713\n\n### Instruction:\nThe codes below do not appear in DHC when exported from DHH:\xa0\r\n\r\n7900.0025 (new code)\r\n6700NM.025EN (new code)\r\n6900.025EN (12th version)\n\n### Response:\n["Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", \'Comment 2: "hi\', \'Comment 3: I\\\'m using Kotrak1 account and I do not have an access to UAAPP03 (10.106.25.38) server!image-2023-03-08-16-41-19-769.png!I can only login intoUADB03 (10.106.25.32)and I see only test databases!image-2023-03-08-16-42-28-051.png!I can not open DHP as well!image-2023-03-08-16-44-42-122.png!To verify this issue I need access to DHC (App and Database) and DHP (App and DB).Please check."\', "Comment 4: \'Marta moved everything to other new working servers", "Comment 5: this was still at the beginning of January:DHP database - UADB02 10.106.25.31DHP application - UAAPP02 10.106.25.37 http://10.106.25.37/#/loginDHC database - UADB01 10.106.25.30DHC application - UAAPP01 10.106.25.36\'", "Comment 6: \'konfiguracja w dhh wydaje się być poprawna !image-2023-03-08-19-07-27-412.png!w logach synchronizacji dhc czystow logach BP brak komunikatów dot itemchange w kontekście badnych towarówponowne wysłanie itemów z dhh nic nie dajew logach z GatewayPlugin (C:\\\\\\\\Kotrak\\\\\\\\GatewayPlugin_Ukraine) jest komunikat błędu !image-2023-03-08-19-37-57-612.png! kolejka ma około 4600 messagyPo restarcie powoli schodzi\'", "Comment 7: \'Synchronization between DHP and DHP has hanged. It has been restarted. There is more then 4500 messages waiting to be synchronized. Items should be available when queue will end proceed.\'", "Comment 8: \'DHP and DHP ? What did you restart? Why did this happen?\'", "Comment 9: \'!image-2023-03-09-08-18-21-439.png!\'", "Comment 10: \'!image-2023-03-09-08-32-16-760.png!\'", "Comment 11: \'zrestartwana usluga ukraine.gatawey powoli skapuje\'", "Comment 12: \'It seemd that another queue - Ukraine.gateway -was hanged I restarted it and slowly messages are being synchrnized!image-2023-03-09-08-38-38-037.png!\'", "Comment 13: \'We are still waiting for Ukraine.gateway plugin queue to finish. Rest of Ukraine queues in DHH are done.!image-2023-03-09-19-10-36-156.png!\'", "Comment 14: \'How long does it take for this process to be completed?And what was the reason?\'", "Comment 15: \'Nadal na kolejka jest ok 3 tysiecu meassage ( 2960) ostatnie Recipe były importowane 05.03!image-2023-03-10-08-48-07-725.png\|width=619,height=168!!image-2023-03-10-08-59-42-188.png!pingowanie z teraz sa timeouty na łączeniu z serwerem\'", "Comment 16: \'DHH gateway was configured for communication with both systems: production and test.Test system is not responding. Every message from DHH was waiting for response from test system for 30 seconds. We have disabled communiacation to test system in order to optymize synchronization between DHH and production DHC system.Items should be avaible in DHC. Please check.\'", "Comment 17: \'yes", \'Comment 18: we checked and it looks like everything is fine\', "Comment 19: Items now be available in DHC\'", "Comment 20: \'Could you please confirm if we can close this task?Regards\'", "Comment 21: \'yes", "Comment 22: you can close it task\']"]\nRelated Issues:\n[]\n\n### End'}
320	{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8712\n\n### Instruction:\nWe have error in the VT-1342/23, item SUE1605-S25, we have reservation WD-919/3/23, we cancelled because quantity was wrong, but after cancel the item is reserved yet.\r\nCould you please remove reservation, it\'s urgent remove reservation, truck is waiting to load.\r\n\r\nThank you\n\n### Response:\n["Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", \'Comment 2: " !screenshot-1! {code:java}declare @barcode nvarchar(max) = \\\'89-W00AZT\\\'delete srfrom dbo.StockUnits sinner join dbo.StockUnitReservations sr on sr.Id = s.Idwhere s.Barcode = @barcodeupdate dbo.StockUNITSSET QuantityOnhand = Quantitywhere barcode = @barcodeupdate suset su.QuantityOnHandValue=1000,su.ReservedQuantityValue=0,su.ReservationSourceDocumentNumbers=\\\'\\\' FROM [DHPlantWmsBusinessLogicMain].[dbo].[UnitLoads] ul inner join [DHPlantWmsBusinessLogicMain].dbo.StockUnits su on ul.id=su.UnitLoadId where ul.Barcode in(\\\'89-W00AZT\\\') i dla stocka w pcs.{code}"\', "Comment 3: \'Stock unit has been corrected", "Comment 4: please check and send a feedback.\'", "Comment 5: \'I checked and now is correct. Do you know why we have this error? Thank you.\'", "Comment 6: \'DGS-8715 RCA has been created - further analysis will be on this task.Can we close this one?\'", "Comment 7: \'Hi PiotrI just inserted a comment on DGS-8715Can you check it please?Thank you\'", "Comment 8: \'Hello ,The other examples you arę mentioned on RCA task id IT a P1 issue now?Could we close this task or power its priority?\'", "Comment 9: \'Hello,you can close. Thank you.\']"]\nRelated Issues:\n[\'DGS-8715\']\n\n### End'}
321	{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8711\n\n### Instruction:\nDears,\r\n\r\nVT-135/3/23 is in DHP and not in DHC and ERP.\n\n### Response:\n["Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", "Comment 2: \'vte o tym numerze jest 3 razy 2 razy w statusie 1 brak elementów!image-2023-03-08-13-34-17-463.png!\'", "Comment 3: \'!image-2023-03-08-13-36-56-253.png!\'", "Comment 4: \'SELECT TOP (1000) [PlantId] ,[PlantIdNo] ,[LongId] ,[StringId] ,[GuidId] FROM [DHPlantIntegrationDhcServiceIdentityMapping].[dbo].[VehicleTicketIdentityMappings] where longid=108821\'", \'Comment 5: "@ widać tu nadamirowe wpisy 3 razy wszedł ten sam vt ale 2 razy niekompletnie\', \'Comment 6: jest ten sam externalid 3 razy pytanie czy powywalac te wpisy na których brak info o wadze itd ?dla tego id zrobiła update status na 1 z 2\', \'Comment 7: expected quantity z 0 na 1 ake pomimo puszcza wiaodmości rabitem nic sie nie pojawia na elementach.\', \'Comment 8: logów brakpodejrzewam że to że są 3 vt o tym samym externalid jets tu problememid VT w dhc na którym robiłam updaty=\\\'0391AF3B-2FA7-48F1-9A04-BCC227396EFC\\\'"\', "Comment 9: \'!image-2023-03-08-15-04-55-590.png!\'", "Comment 10: \'Please verify it was renchronized to DHC.!image-2023-03-08-15-20-23-803.png!\'", "Comment 11: \'yes", "Comment 12: thanks!\']"]\nRelated Issues:\n[]\n\n### End'}
322	{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8710\n\n### Instruction:\nHi, task from Wiola:\r\n\r\n\n\n### Response:\n["Comment 1: [\'!image!\'", "Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", "Comment 3: \'[^limit_urlopowy_KAJDAS.docx]\'", "Comment 4: \'Explanations in the attachment[^limit_urlopowy_KAJDAS.docx]\'", "Comment 5: \'!image-1!\']"]\nRelated Issues:\n[]\n\n### End'}
323	{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8709\n\n### Instruction:\nBoth item variants and both recipes 302291 in DHC don\'t appear in DHP Nijkerk.\r\n\r\nIn DHC everything looks good.\n\n### Response:\n["Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", "Comment 2: \'Dear Rob,Below is the list of items that should be resynced to DHC Service. Should I process them all?302291130170149999112122149998\'", "Comment 3: \'302291 is resynced and is in plant now.!image-2023-03-08-10-55-07-630.png!\'", "Comment 4: \'Thanks Aleksandra", "Comment 5: please process all of the items to sync. After that the ticket can be closed.Regards,Rob.\'", "Comment 6: \'Dear Rob,Helmond:!image-2023-03-08-11-17-29-220.png!Maasbracht:!image-2023-03-08-11-18-37-250.png!Recipe 149998 and 149999 are for plant Balgoji which is not supported by Kotrak. I have resynced them in DHC", "Comment 7: they are in DHC Service now.!image-2023-03-08-11-23-29-433.png!Regards\'", "Comment 8: \'Zrobiłam jeszcze restart BP", "Comment 9: bo cosik się przytykało znowu!image-2023-03-08-11-33-36-722.png!\'", "Comment 10: \'I can see the Balgoij items/recipes are picked up by WebMethods.Thanks for your support", "Comment 11: the ticket can be closed.Regards,Rob.\']"]\nRelated Issues:\n[]\n\n### End'}
324	{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8708\n\n### Instruction:\nOrders do not arrive in DHP Maasbracht anymore: examples:\r\nSOBE000016241\r\nSOBE000016242\r\n\r\nAlso shipping notices related to these orders do not arrive\r\nForeignNumber: L000150977\r\n\r\nCan you please check. They need to be loaded tomorrow morning first trip, so they must be in the plant before 22:00 tonight.\n\n### Response:\n["Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", "Comment 2: \'Both orders are avaible in DHP!image-2023-03-07-19-28-43-556.png!as well as SN!image-2023-03-07-19-31-47-963.png!Please check\'", "Comment 3: \'Yup", "Comment 4: they did arrive. The processing of messages in the DHC Queue was very slow.But you can close this ticket\']"]\nRelated Issues:\n[]\n\n### End'}
325	{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8707\n\n### Instruction:\nI tried to create opening balance for Andel_mest, but the process hangs in status processing: What is going wrong?\r\n\r\nAlternatively I can create stock on Andel-West and split it to Andel-Mest but in 8.5 I don\'t have this option?\n\n### Response:\n["Comment 1: [\'!afbeelding!\'", "Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", "Comment 3: \'!image-2023-03-07-15-49-22-969.png!\'", "Comment 4: \'System.FormatException: Index (zero based) must be greater than or equal to zero and less than the size of the argument list.\'", "Comment 5: \'Could you please provide file you are using for OB?\'", "Comment 6: \'see attached[^Andel.xlsx] _(12 kB)_\'", "Comment 7: \'[[email protected]]hej Maciej mówił żebyś pomogła spojrzeć na ten plik", \'Comment 8: co podeslał Thomas\', "Comment 9: bo prawdopodobnie z nim jest problem\'", "Comment 10: \'[[email protected]] W pliku załączonym przez Thomasa LocationCode jest lokalizacją należącą do Andel-Mest", \'Comment 11: natomiast wpisany OwnerName i BusinessUnitName to Andel-West. Jeśli chce zrobić OB dla Andel-Mest\', \'Comment 12: to musi zmienić OwnerName i BusinessUnitName na "098 Andel (fertilizer) NL".!OB_2bu\\\\\\\'! !BU_location!\\\'\', \'Comment 13: "any update\', \'Comment 14: it\\\'s causing delays now because orders cannot be finished"\', "Comment 15: \'[[email protected]]Hello,in your OB file", \'Comment 16: the entered location is from Andel-Mest but owner and BU is from Andel-West. !BU_location! Please change the OwnerName i BusinessUnitName to "098 Andel (fertilizer) NL" and it should work: [^Andel_98-1.xlsx]\\\'\', \'Comment 17: "Thanks! this works\', \'Comment 18: I tried that combination before but I think I mist a space or sometinh in the BU name. anywhay\', "Comment 19: it\'s solved. Additional question: why can\'t I move/split stock from andel-Mest to Andel-West or vice versa? For bulk this option is available", \'Comment 20: for packed goods not"\', "Comment 21: \'Fast movement and split of packed UL is available on the unit loads list in the WMS module. !screenshot-1! \'", "Comment 22: \'May we close the task?\'", "Comment 23: \'If I try to split I cannot select location Andel-MEst", \'Comment 24: when I try Fast movement I get below error\', "Comment 25: do we miss configuration again?!afbeelding-1!\'", "Comment 26: \'[[email protected]]Hi", "Comment 27: I added missing configuration for the 2nd BU. It should be possible now. !WMS_transfer location! \'", "Comment 28: \'It is all working now> May we close this task?\'", \'Comment 29: "It\\\'s oke now\', \'Comment 30: thanks"]\']\nRelated Issues:\n[]\n\n### End'}
326	{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8706\n\n### Instruction:\nHi\r\n\r\nWe created the VT-1320/23 we weighted the truck, however when Releasing for dispatch system shows an error message: An unexpected error occurred. Please contact system help desk.\r\n\r\nOne particular thing that happened with this VT is that when creating, the operator wrongly selected the Paking type = Bulk, but the item is packed. Then the operator detached the bulk item from VT and inserted it again as packed.\r\n\r\nCould you please help us?\r\n\r\nThe truck is waiting to load the items, but without releasing we can\'t open WO on mobile.\r\n\r\nThank you\n\n### Response:\n["Comment 1: [\'!image!\'", "Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", "Comment 3: \'We have the same error when we click in release for intake!image-1!\'", "Comment 4: \'od 2.marca nie loguje w module VC !screenshot-1! \'", "Comment 5: \'prośba o pomoc w ustaleniu przyczyny błędu", "Comment 6: np.w logach z VC nie loguje nic od 2.marca(mimo wywołania błędu).\'", "Comment 7: \'Guys", "Comment 8: any news?We have another VT intake VT-1366/23 with error to Complete the VTCould you please check?\'", "Comment 9: \'[[email protected]] Macka już nie ma w biurze. Nie pomoże nam dzisiaj\'", "Comment 10: \'[[email protected]] niech wystawią może nowe VT. Logami się Maciek jutro zajmie\'", "Comment 11: \'Analysis of this situation will take some time. An an workaround please generate new VT document.\'", "Comment 12: \'Hi BartłomiejThank you for your feedback!We created a new VT document and this new one worked perfect fine.But we need to find the reason why this VT-1320 crashed.Thank you\'", "Comment 13: \'Can we lower this issue priority to P2 then.\'", "Comment 14: \'Yes! You can\'", "Comment 15: \'[[email protected]] for this VT Arrival date is null.DHITS-721!image-2023-03-08-13-01-33-048!!image-2023-03-08-13-02-49-019!In this task we have 2 cases: 1) VT-1320 created status => DHITS-721 (DAP - update available in 8.6) ; 2) VT-1366 in progress status => we will check in DAP projectFor VT-1366 we have several users who worked on this document:* user tgrassi started to work on this document* next user isantos worked on this document!image-2023-03-08-15-49-25-930!* and when user isantos finished with this document", \'Comment 16: after that user tgrassi finished too!image-2023-03-08-15-53-33-991!* as you know this the diff between 3.0 and 2.5 ; in 2.5 you had a sessionId on documents. Now\', \'Comment 17: you have web applications\', "Comment 18: and several users can work on the same document in the same time (edit) \'", "Comment 19: \'[[email protected]] jeśli chodzi o brak logów to jest to związane z tym", \'Comment 20: że w tasku DGS-8678 usunęli grupę users\', \'Comment 21: która miała dostęp do folderu IIS. Grupę tą potem dodaliśmy. Natomiast nie miała ona specjalnych uprawnień. Podczas instalacji i konfiguracji\', \'Comment 22: podczas uruchomienia IIS zostają dodane wszystkie potrzebne uprawnienia. Natomiast podczas ręcznego dodanie tej grupy\', "Comment 23: uprawnienia specjalne nie zostały dodane (nie mamy takiej możliwości z UI). Stąd [[email protected]] jutro rano doda te uprawnienia skryptem.\'", \'Comment 24: "Hi [[email protected]]That\\\'s weird because when you enter the VT document you can find the Arrival date in there!image-2!!image-3!"\', "Comment 25: \'PLUS: What do we need to do to fix?We created new VT documento for VT-1320", \'Comment 26: so it will be canceledBut for VT-1366 we are still waiting to complete\', "Comment 27: PLRs is waiting to consume this SUCould you please fix that?thank you\'", "Comment 28: \'Hi", "Comment 29: date that is missing !screenshot-2! Corrected from ArrivalWeighingDate.\'", \'Comment 30: "[[email protected]] you are right\', \'Comment 31: you have ArrivalWeighingDate\', \'Comment 32: but you don\\\'t have ArrivalDate. "\', "Comment 33: \'[[email protected]]dzisiaj [[email protected]] dodał odpowiednie uprawnienia do folderów dhp dla IIS. Restart IIS został dzisiaj rano po godz. 7 naszego czasu wykonany. Pliki logs tworzą się per moduł.\'", "Comment 34: \'Hello guysNow VT is closed!Thank you very much!You can close this task\'", "Comment 35: \'[[email protected]] fix will be available in 8.6.\']"]\nRelated Issues:\n[\'DGS-8678\', \'DAP-13410\']\n\n### End'}
327	{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8705\n\n### Instruction:\nMitch told us that in the upcoming days the functionality of automatically closing rounds, feed sales and financial statements once the saldo 2 pay is closed, will be introduced in PROD. In MAS BE, we do have most S2P\'s closed, but not every round+feed sale linked to this S2P and and no FS yet. Could you let all rounds, feed sales and financial statements (= all linked documents to these rounds) close for the S2P\'s that are archived yet?\n\n### Response:\n["Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", \'Comment 2: "Hi Steffen,Indeed we will move soon to prod environment these changes - If the user sends S2P to Archive via flow\', \'Comment 3: others documents such as FS\', \'Comment 4: Round and Feed sale will also be in Archived status.We can prepare action to closing Financial Statement\', \'Comment 5: Round and Feed sale for Archived S2P documents.Should we sent all these documents for already Archived S2P\\\'s in MAS BE?@MitchShould we also sent these documents also in other sectors like in MAS BE?Regards"\', "Comment 6: \'Should we also sent these documents also in other sectors like in MAS BE? --> yes please do it as well for MAS NL. \'", "Comment 7: \'Hi [[email protected]],the functionality of automatically closing Rounds", \'Comment 8: Feed sales and Financial Statements for Saldo to pay has been moved into prod Intense environment.Also\', "Comment 9: we\\\\\'ve cloned this functionality for all sectors in test Intense environment. You can verify it.Now", \'Comment 10: we are focusing on second part of task - closing documents related to Saldo to pay document in "Archived" status.Best regards,Grzegorz\\\'\', \'Comment 11: "Does the FS not archive automatically when S2P is archived? It seems to be an approval flow but can\\\'t it be a direct archive like the S2P?"\', \'Comment 12: "And the same for Feed sales? The round was closed automatically\', \'Comment 13: but the feed sale (and financial statement) wasn\\\'t."\', "Comment 14: \'The FS and Feed sales should indeed be automatically closed as well.\'", \'Comment 15: "[[email protected]],we\\\'ve missed new flows in process definition for Financial Statement. Right now\', \'Comment 16: everything is correctly. So you can try it again.Best regards,Grzegorz"\', "Comment 17: \'Hello Grzegorz,This seems indeed to be working now.\'", "Comment 18: \'Przygotowane zapytania pod archiwizację dokumentów związanych niezarchiwizowanych.Do archiwizacji dokumenty historyczne.\'", "Comment 19: \'Is this fixed right now?\'", \'Comment 20: "On production environment right now is implemented this solution: If the user sends S2P to Archive via flow\', \'Comment 21: others documents such as FS\', \'Comment 22: Round and Feed sale will also be in Archived status.It\\\'s implemented in MAS NL and MAS BE sectors only as it was set before.The only thing left in this topic is to archive historical documents. We\\\'re working on it and we\\\'ll inform in task when it will be ready.When it will be done I think we can close this task and also linked to it https://helpdesk.kotrak.com/browse/DHNLC-1147"\', "Comment 23: \'Wszystkie FS spięte z archiwalnymi S2P zostały przesłane do Archiwum.Do przesłania pozostały Roundy.\'", \'Comment 24: "All Financial statements in MAS NL and MAS BE right now have been sent to Archive when linked S2P have been sent to Archive.Only Round documents and Feed sale left and will be sent to Archive. We\\\'ll inform you when it\\\'s done."\', "Comment 25: \'Do wrzucenia selecty dla rundy i FS", "Comment 26: które służą do przesyłania dokumentów do archiwum.\'", "Comment 27: \'[^DGS-8705_SelectDataForAutomaticFlow(S2P,FS,Rounds).txt]\']"]\nRelated Issues:\n[\'DGS-8897\']\n\n### End'}
328	{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8704\n\n### Instruction:\nThe item 22064, lot number WI-88/1/23-1 is with reservation of production 0871260123017, but the production is already confirmed. Could you check why reservation didn\'t disappear?\r\n\r\nthank you\r\n\n\n### Response:\n["Comment 1: [\'!image!\'", "Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", \'Comment 3: "{code:java}update suset su.ReservationSourceDocumentNumbers=\\\'\\\' FROM [DHPlantWmsBusinessLogicMain].[dbo].[UnitLoads] ul inner join [DHPlantWmsBusinessLogicMain].dbo.StockUnits su on ul.id=su.UnitLoadId where ul.Barcode in(\\\'87-W0020R\\\'){code}"\', "Comment 4: \'Hello. Data has been corrected.According to RCA DGS-8168 PLR reservations have been corrected for version 8.5\'", "Comment 5: \'Hello Piotr,Ok", "Comment 6: you can close this task. Thank you.\']"]\nRelated Issues:\n[]\n\n### End'}
329	{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8703\n\n### Instruction:\nHello,\r\n\r\nthese orders are not in VC-Module, but also I cannot find anything in the error log, so I\'m not sure whats going on and what needs to be done to fix this, please check\n\n### Response:\n["Comment 1: [\'ogólnie nie było errów", \'Comment 2: logi czyste po pownownej wysyłce do MAssbracht jeden wisiał był errorPonowna wysyłka i pomogło wczesniej 2023-03-06 15:38:48 (/Plant.VC.BusinessLogic/DHVD01AP178/14580/48)[Error]Kotrak.Extensions.Pipeline.CatchPipeline - Pipeline execution errorSystem.NullReferenceException: Object reference not set to an instance of an object.at Kotrak.Common.PublishedLanguage.User.Equals(User other)at <>f__AnonymousType0`3.Equals(Object value)at System.Linq.Lookup`2.GetGrouping(TKey key\', \'Comment 3: Boolean create)at System.Linq.Lookup`2.Create(IEnumerable`1 source\', \'Comment 4: Func`2 keySelector\', "Comment 5: IEqualityComparer`1 comparer)at System.Linq.GroupedEnumerable`2.GetEnumerator()at Kotrak.Common.Infrastructure.Integration.Filters.InboundMessageAcknowledgeHandlerFilter.Execute(InternalStorageContext`1 input)at Kotrak.Extensions.Pipeline.Pipeline`1.Execute(T input)at Kotrak.Extensions.Pipeline.CatchPipeline`1.Execute(TContext input)Wysłany ponownie przeszedł.Pierowtnie jeśli chodzi o obie fabryki ordery szły do dhp o róznych godzinach i dniach więc raczej to nie kwestia jednorazowa.\'", "Comment 6: \'selectFROM [DHPlantMaintBusinessLogicMain].[dbo].[Orders] where year =2023 and IsInVehicleControl=0 and month=3 and type=2\'", "Comment 7: \'Masbracht stan na dziś!image-2023-03-09-13-32-22-179.png!\'", "Comment 8: \'nie w VC extarnelid208390 208748 207387 206487 207851 208832 208423 208678 208173Pierwotnie wysyłka w takich godzinach!image-2023-03-09-13-35-57-792.png!select from OrderExportInfoes where entityid in ( select id from Orders where externalId in (208390,208748,207387,206487,207851,208832,208423,208678,208173))!image-2023-03-09-13-35-57-792!\'", "Comment 9: \'!image-2023-03-09-13-42-54-335.png\|width=893,height=341!brak błędów\'", \'Comment 10: "na bazie intercontekstów też czysto tylko kilka errorw z 01.03.!image-2023-03-09-13-47-42-108.png!Przykład wybranego ordera na eventach : FROM [DHPlantVCBusinessLogicEvents].[dbo].[Orders] where AggregateId =\\\'C66329A4-FA5E-47BE-BE2C-33F7427F015D\\\'[[email protected]]prośba odemnie i Maciej o sprawdzenie co tam się dzieje."\', "Comment 11: \'Hello", \'Comment 12: please check: I can see this case now for multipe locations: I added screenshot for Veghel\', \'Comment 13: Helmond\', "Comment 14: Maasbracht but please check also other locations!!afbeelding-2!!afbeelding-3!!afbeelding-4!\'", "Comment 15: \'Problem z maintenance zgłoszony w DAP-13415!image-2023-03-15-10-03-50-960!\'", "Comment 16: \'Hello [[email protected]]as I informed you in other task problem is only with wrong information in the masterdate table - we are working on solution.\']"]\nRelated Issues:\n[\'DGS-8690\', \'DAP-13415\', \'DGS-8763\']\n\n### End'}
330	{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8702\n\n### Instruction:\nHello,\r\n\r\nuser tries to complete a WMO for Andel-Mest, but get message No default dispatch location configured: where can we do this? See screenshot. The Warehouse order = WO(PD)-40/3/23\n\n### Response:\n["Comment 1: [\'!afbeelding!\'", "Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", "Comment 3: \'!image-2023-03-07-12-50-48-176.png!\'", "Comment 4: \'Dear Thomas,Please", "Comment 5: check now and let me know if this is correct:!image-2023-03-07-12-54-19-757.png!Regards\'", "Comment 6: \'I have consulted it and it should be truck:!image-2023-03-07-13-03-41-508.png\|width=1176,height=289!But you need to configure truck here!image-2023-03-07-13-06-31-673.png!Like for West:!image-2023-03-07-13-07-06-713.png!It would be also fine to remember about release:!image-2023-03-07-13-08-22-091.png!Regards\'", "Comment 7: \'Thanks aleksandra", "Comment 8: so I should create a truck and release location for Andel-mest? Or do I misunderstand?\'", "Comment 9: \'Yes", \'Comment 10: exactly. Create a truck and release location. Because it is highly possible that error about release location may appear. If you need any help\', \'Comment 11: please\', "Comment 12: let us know :)\'", "Comment 13: \'Oke", "Comment 14: I;ve created those. Thanks for the help you can close the ticket\'", "Comment 15: \'Thank you.Regards\'", \'Comment 16: "Sorry I\\\'ve one additional question: since release 8.5 I cannot move stock from Andel_West to Andel_mest\', \'Comment 17: for example for these products: How to handle this\', \'Comment 18: because I need those on Andel Mest location!afbeelding-1!"\', "Comment 19: \'It should be done from here - unit loads list", "Comment 20: not stock unit list :)!image-2023-03-07-14-44-48-414.png!\']"]\nRelated Issues:\n[]\n\n### End'}
331	{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8701\n\n### Instruction:\nIt\'s needed to add new relation in relation table and adjust in the system.\r\n\r\n!image-2023-03-07-11-23-19-479.png!\n\n### Response:\n["Comment 1: [\'https://app.box.com/file/1002580990454?s=kf5ux29gz5g5k2ykm5a6fz47a75n7741Do poprawy w przypadku nieobsługiwania którejś kolumny w Tabeli Relacji (nie wszystkie punkty są wymagane dla każdego sektora):\|1.\|Round\|\|2.\|Round -> Create Financial Statement (Create Sales Invoice from Round)\|\|+3.+\|FS - General\|\|4.\|FS - Details Total\|\|5.\|FS - Details Table with invoice lines\|\|6.\|FS - saldo\|\|7.\|FS - Tech Results (Calculate Technical Results)\|\|8.\|FS -> Create Saldo to Pay\|\|9.\|FS - printouts procedures\|\'", "Comment 2: \'!image-2023-04-17-09-44-22-647.png!\'", "Comment 3: \'New realtions added to test database.\'", "Comment 4: \'Can be moved to PROD\']"]\nRelated Issues:\n[]\n\n### End'}
332	{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8700\n\n### Instruction:\nMamy error ID6344142 nie jesteśmy w stanie odczytać czego on dotyczy. Dane przestały spływać do DHP. Temat Bardzo Pilny..!\r\n\n\n### Response:\n["Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", "Comment 2: \'Produkcja zatrzymana właśnie \'", "Comment 3: \'message that was blocked for pcsLotId=230307010there was no StartTransferu Not found open transfer for this route\'", \'Comment 4: "Now it\\\'s better"\', "Comment 5: \'Thank you for confirmation.\']"]\nRelated Issues:\n[]\n\n### End'}
333	{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8699\n\n### Instruction:\nprośba o bezpośredni kontakt kogoś technicznego z Jarkiem w sprawie weryfikacji podłączenia wagi ekspedycyjnej w Golubiu, na ten moment odczyt jest poprawny, ale podczas przełączania się na inną wagę, albo zapisu system się zawiesza, Jarek ma jakiś pomysł\n\n### Response:\n["Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", "Comment 2: \'Problem z wagami - nie konfigurowane przez nas - robione na wzór Spytkowic gdzie Ewelina przekazała my konfigurowaliśmy ale to było lata temu.Problem jest przy przełączaniu wag z poziomu VT.Dzwoniłem na fabrykę dostałem tyle informacji że konwerter łączy z wagą i przy przełączeniu nie zrywa połączenia z wagą wcześniej wybraną. \'", "Comment 3: \'Hi Ewelina", "Comment 4: the issue has been changed from incident to service request.\'", "Comment 5: \'podobna sytuacja z wagą ekspedycyjną jest w Spytkowicach", \'Comment 6: tylko tam nawet nie ma odczytu\', \'Comment 7: zweryfikujcie to proszę\', \'Comment 8: bo w Spytkowicach była ustawiana jeszcze dawno dawno temu przez Was\', "Comment 9: a w Golubiu sami próbowaliśmy to odwzorować\'", "Comment 10: \'Temat gdzie w zgłoszonym Golubiu konfigurowali wagi na wzór Spytkowic", "Comment 11: prośba o wsparcie w temacie.\\\\rW Spytkowicach też jest problem ale nie wiem jak się do tego odnieść jak to było robione lata temu co przekazała Ewelina.\'", "Comment 12: \'any news?\'", "Comment 13: \'any news?\'", "Comment 14: \'tak wygląda w Spytkowicach!image!\'", "Comment 15: \'!image-1!\'", "Comment 16: \'!image-2!\']"]\nRelated Issues:\n[]\n\n### End'}
334	{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8698\n\n### Instruction:\nCould you please migrate the three migration files in this task?\n\n### Response:\n["Comment 1: [\'[^AA - NAS_Migration_PURCHASEINVOICE_workfile_007590.xlsx] _(127 kB)_[^AA - NAS_Migration_SALESINVOICE_workfile_007590.xlsx] _(610 kB)_[^Feed migration_NAS 007590.xlsx] _(112 kB)_\'", "Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", \'Comment 3: \\\'Hi [[email protected]],\\\\r\\\\rwe have missing values in column "Amount "in Feed migration file. Could you provide the correct values?\\\\r\\\\rBest regards,\\\\r Grzegorz\\\'\', \'Comment 4: "What is the column name and what lines? I don\\\'t see any missing values in my file.Or don\\\'t you refer to the Feed migration file?"\', "Comment 5: \'Sales and Purchase Invoices have been migrated to the Intense in prod environment.We are waiting for the correct Feed sale file.Best regards,Grzegorz\'", \'Comment 6: \\\'[[email protected]],the "Quantity" column:!image-2023-03-13-13-23-51-931.png!\\\'\', "Comment 7: \'I see. this is always 1. Could you change this for me?\'", "Comment 8: \'[[email protected]],thank you for the answer. Feed sale elements have been migrated too.Best regards,Grzegorz\'", "Comment 9: \'Hi [[email protected]],can we close the task?Best regards,Grzegorz\'", "Comment 10: \'Yes\'", \'Comment 11: "Thank you for your reply.I\\\'m closing the task.Best regards,Grzegorz"]\']\nRelated Issues:\n[]\n\n### End'}
335	{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8697\n\n### Instruction:\nSee SI Numbers\n\n### Response:\n["Comment 1: [\'!image!\'", "Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", "Comment 3: \'Hello,8 lines with these invoice numbersSI000038161", \'Comment 4: SI000021521\', \'Comment 5: SI000055038\', "Comment 6: SI000071217,SI000091258 have been moved to the feed saleFE-N/0109 (Round007590/0076/0001)!image-2023-03-07-11-39-31-353.png!Regards\'", "Comment 7: \'{color:black}Hello,{color} {color:black}{color} {color:black}Thankx", \'Comment 8: you can close it.{color} {color:black}{color} \| \|{color:#000001} Metvriendelijkegroet,{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:#000001}{color} \| \| \| \|{color:#000001} Bert{color} \|{color:#000001} {color} \|{color:#000001} Geijtenbeek{color} \| {color:#000001}MedewerkerContractadministratie{color} \| \| \|{color:black}{color} {color:black}{color}{color:windowtext}{color}{color:black}{color}!image001!{color:black} <[https://www.de-heus.nl/]>{color} \| \| {color:#006FB7} DEHEUSVOEDERSB.V.{color} \| \| \| \|{color:#000001} Postbus396 6710BJEde \\\\u200b{color} \| \|{color:#000001} Rubensstraat175 6717VEEde \\\\u200b{color} \| \| \|{color:#000001} T:0318675561{color} \| {color:#000001}KvK14626985{color} _{color:#000001} _Opdite‑mailberichteneventuelebijlage(n)isdedisclaimervantoepassing_ _gepubliceerdopdewebsitevan_ {color}[{color:#000001}{color}{color:#000001} _+ DeHeusVoeders+_{color}{color:#000001} {color}\|https://www.de-heus.nl/privacy-beleid]{color:#000001} _._{color}_ \| \| !image002! <[https://www.facebook.com/deheusvoeders]>{color:black}{color} \| \| !image003! <[https://twitter.com/de_heus_voeders]>{color:black}{color} \| \| !image004! <[https://www.youtube.com/channel/UCqkrGebUlFowgumurz-abxQ]>{color:black}{color} \| \| !image005! <[https://www.linkedin.com/company/de-heus-voeders-b-v-/]>{color:black}{color} \| Van: Damian Świstek (Jira) <[email protected]> Verzonden: dinsdag 7 maart 2023 11:43 Aan: Geijtenbeek\', "Comment 9: Bert <[email protected]> Onderwerp: DGS-8697 Move feed 807590/0045/0001 > 007590/0076/0001 !image006!\']"]\nRelated Issues:\n[]\n\n### End'}
336	{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8696\n\n### Instruction:\nHi\r\n\r\nWe have this WO(IP)-152/3/23 with a lot UL generated and registered wrongly.\r\nThe user created the UL as BigBag, however this must be a pallet.\r\nWhen we try to remove the registered UL, system displays an error message: {color:red}Warehouse intake should be in progress{color}\r\n\r\nCould you please withdraw ALL the registered UL from this WO(IP)?\r\nThe truck is waiting for it.\r\n\r\nThank you very much\n\n### Response:\n["Comment 1: [\'!image!\'", "Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", "Comment 3: \'Elements has been removed from WI-307/3/23 related to WO(IP)-152/3/23. Unfortunatly there id one barcode 89-W006LS that has been released on STK-159/3/23.!image-2023-03-06-17-14-22-169.png!!image-2023-03-06-17-15-56-077.png!That is why i can not remove it from WI-307/3/23.You can create one addidtional element related onWO(IP)-152/3/23 for this extra quantity. and correct it through stocktaking if nessesery.Please check an let us know if we can close this issue.\'", "Comment 4: \'Hi BartłomiejThank you very much!You can close this task\'", \'Comment 5: "weryfikacja{code:java}SELECT TOP (1000) * FROM [DHPlantWmsBusinessLogicMain].[dbo].WarehouseOrders where DocumentYear=2023 and DocumentMonth=3 and DocumentNumber=152select Status,* from dbo.WarehouseIntakes where DocumentNumber=307 and DocumentYear=2023select * from dbo.WarehouseIntakeElements where Id=\\\'A3E8C981-82B9-4155-8226-499496C3F13C\\\'select * from dbo.UnitLoads where Id in (\\\'3D3074DB-1C22-45C7-8C4F-0A039971B268\\\',\\\'D6A1F9B5-6323-4953-86BF-47ABAA0079B9\\\',\\\'329E416C-16FF-4B7A-86B0-5E458B23A0F6\\\',\\\'7140933B-33AB-42D1-976C-8520960E03F8\\\',\\\'931E3BE8-DE3F-422C-81D9-81A1257F7256\\\',\\\'19BEF811-6D16-493A-8AFC-2111C9531DFD\\\',\\\'FFD8D6A2-1D4F-4E6E-B670-1C1A013FB539\\\',\\\'06742CBC-F081-46D5-944A-D1D738B48397\\\')select * from dbo.StockUnits where UnitLoadId in (\\\'3D3074DB-1C22-45C7-8C4F-0A039971B268\\\',\\\'D6A1F9B5-6323-4953-86BF-47ABAA0079B9\\\',\\\'329E416C-16FF-4B7A-86B0-5E458B23A0F6\\\',\\\'7140933B-33AB-42D1-976C-8520960E03F8\\\',\\\'931E3BE8-DE3F-422C-81D9-81A1257F7256\\\',\\\'19BEF811-6D16-493A-8AFC-2111C9531DFD\\\',\\\'FFD8D6A2-1D4F-4E6E-B670-1C1A013FB539\\\',\\\'06742CBC-F081-46D5-944A-D1D738B48397\\\')SELECT TOP (1000) * FROM [DHPlantWmsBusinessLogicMain].[dbo].[StockUnitReleases] where Id = \\\'3B89A29C-2A29-4561-A808-B740A20D47F5\\\'{code}rozwiązanie tylko gdy nie ma powiązanych dokumentów{code:java}--update dbo.WarehouseIntakes set Status=30 where id = \\\'A3E8C981-82B9-4155-8226-499496C3F13C\\\'{code}"]\']\nRelated Issues:\n[]\n\n### End'}
337	{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8695\n\n### Instruction:\nFor some reason, round 2 became B001422/0172/0004, round 3 was correct (B001422/0172/0003) and round 4 became B001422/0172/0005. Could you adapt round 2 (B001422/0172/0004, ID 71622) to number B001422/0172/0002 and round 4 (B001422/0172/0005, ID 99850) to number B001422/0172/0004? So the round numbers are good, but the full round numbers are wrong.\n\n### Response:\n["Comment 1: [\'!image!!image-1!\'", "Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", \'Comment 3: "Hello Steffen,Yes\', "Comment 4: it\'s strange that there is no number B001422/0172/0002 at all in Intense right now. Maybe there were some changes in customer on roundB001422/0172/0004 then Intense coul recalculate full number (originally probably was round 2 like order of ID\'s) because generally full number should be ascending like ID", "Comment 5: but in this case it\'s not. I think other documents for this rounds have good number round like this PI below!image-2023-03-07-11-55-23-870.png!!image-2023-03-07-12-04-39-186.png!We can update full round numbers", \'Comment 6: so I\\\'ll let you know when it will be ready.Regards"\', "Comment 7: \'Full round numbers have been updated", "Comment 8: so now round 2 and round 4 have good full numbers!image-2023-03-07-12-41-08-570.png!Please verify that everything is correct.Regards\'", "Comment 9: \'This seems perfect", "Comment 10: thank you!!image-2!\'", "Comment 11: \'Great", "Comment 12: so I close the task.\']"]\nRelated Issues:\n[]\n\n### End'}
338	{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8694\n\n### Instruction:\nPlease resend all lot reports with status confirmed for locations: Helmond, Ravenstein, Maasbracht, Veghel and Andel\r\n\r\nDue to missing configuration with release 8.5 the lot reports in this status are not send to DHC, while they should be. Discussed with Marek and he asked to create this ticket\n\n### Response:\n[\'Comment 1: ["sorry\', \'Comment 2: should be with status \\\'finished\\\'"\', "Comment 3: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", "Comment 4: \'Edit: wszystkie PLRy do wysłania w plikach excel. A było ich .... dużoHelmond - 60 Ravenstein - 9 Maasbracht - 115 Veghel - 8 Andel - 0------------------Razem: 192\'", "Comment 5: \'Do przesłania PLR w statusie Finished wygenerowane odpowiednio dla kolejnych fabryk pomiędzy:\|Date\|Start time\|Plant\|\|28-feb\|09:00\|Ravenstein\|\|1-mrt\|09:00\|Maasbracht\|\|2-mrt\|09:00\|Veghel\|\|3-mrt\|09:00\|Andel\|a 07.03 - 14:55\'", "Comment 6: \'zatem ilość się nie zmieni:Pa jeśli chodzi o Helmond", \'Comment 7: to rozumiem\', "Comment 8: że od samego początku czyli uruchomienia?\'", "Comment 9: \'0041060323025 - RavensteinTu chyba sami sobie je potwierdzili w czasie naszej rozkimny!image-2023-03-07-09-00-32-087.png!!image-2023-03-07-09-01-24-577.png! !image-2023-03-07-09-00-32-087!!image-2023-03-07-09-01-24-577!\'", "Comment 10: \'0081060323049 - Veghel\'", "Comment 11: \'Helmond - od uruchomienia 4 luty do 14 lutego 11:30 - potem został zmieniony config i PLR już wapdają\'", "Comment 12: \'[^DGS-8694.xlsx]\'", "Comment 13: \'[^DGS-8694.xlsx]\'", "Comment 14: \'Skrypt do przerobienia pod 8.5: http://10.10.10.52:82/projects/PLA3/repos/dhp30implementations/browse/NL%20AS400/Scripts/Resend%20draft%20production%20lots%20to%20DHC.sql\'", "Comment 15: \'Veghel:Wszystkie z wczorajszej listy z excela są w DHCW Veghel w plancie jest jeden z teraz:!image-2023-03-08-13-08-47-278.png!!image-2023-03-08-13-07-49-546.png!\'", "Comment 16: \'MAASBRACHT ostatni do przesłania na zółto:!image-2023-03-08-13-14-38-560.png!\'", "Comment 17: \'[^Thomas.xlsx]\'", "Comment 18: \'Dear Thomas,In attach", "Comment 19: here is the list of PLRs sent in the time frame provided by Marek[^Thomas.xlsx]Regards\'", "Comment 20: \'[^dgs-8694 v2.xlsx]\'", "Comment 21: \'[^dgs-8694 v2.xlsx]\'", "Comment 22: \'[^Resend draft production lots to DHC v8.5 (1).sql]\'", "Comment 23: \'[^Resend draft production lots to DHC v8.5 (1).sql]\'", "Comment 24: \'Thanks! ticket can be closed\'", "Comment 25: \'Thank you\']"]\nRelated Issues:\n[\'DGS-8884\']\n\n### End'}
339	{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8693\n\n### Instruction:\nHello,\r\n\r\nin Ravenstein I tried to close VT-36/3/23: added missing quanities and closed the ticket: AS you can see in the screenshot attached it did use the finished product, however status is still \'dispatch completed\' and now it has missing quantities of all orderlines..\n\n### Response:\n["Comment 1: [\'!afbeelding!\'", "Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", "Comment 3: \'Błąd dla stocka{code:java}Kotrak.Common.Application.Exceptions.BusinessLogicException: CannotCompleteBulkWhenRequestedQuantityGraterThanReservedQuantityEvenAutomaticStocktakingIsGeneratedMessage at Plant.Stock.BusinessLogic.Application.Services.RegisterDispatchService.ThrowExceptionWhenCompleteBulkDispatchNotSatisfied(BulkDispatchValidationResult validationResult) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\99f3ad74a1ed56c8\\\\\\\\Plant.Stock.BusinessLogic\\\\\\\\Application\\\\\\\\Services\\\\\\\\RegisterDispatchService.cs:line 421 at Plant.Stock.BusinessLogic.Application.Services.RegisterDispatchService.CompleteBulkDispatch(CompleteBulkDispatchDataStructure dataStructure) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\99f3ad74a1ed56c8\\\\\\\\Plant.Stock.BusinessLogic\\\\\\\\Application\\\\\\\\Services\\\\\\\\RegisterDispatchService.cs:line 306 at Plant.Stock.BusinessLogic.Application.CommandHandlers.BulkDispatch.CompleteBulkDispatchCommandHandler.Handle(CompleteBulkDispatchCommand command) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\99f3ad74a1ed56c8\\\\\\\\Plant.Stock.BusinessLogic\\\\\\\\Application\\\\\\\\CommandHandlers\\\\\\\\BulkDispatch\\\\\\\\CompleteBulkDispatchCommandHandler.cs:line 34 at Kotrak.Common.Infrastructure.Gate.CommandEnvironment.Run[TCommand](TCommand command) at Castle.DynamicProxy.AbstractInvocation.Proceed() at Kotrak.Common.Infrastructure.Interceptors.LoggingInterceptor`1.Intercept(IInvocation invocation) at Castle.DynamicProxy.AbstractInvocation.Proceed() at Kotrak.Common.Infrastructure.Gate.Filters.CommandProcessFilter`1.Execute(CommandPipelineContext`1 input) at Kotrak.Extensions.Pipeline.PredefinedFilters.FilterDecorator`1.Execute(TContext input) at Kotrak.Extensions.Pipeline.Pipeline`1.Execute(T input) at Kotrak.Common.Infrastructure.Gate.StandardGate.DispatchCommand[TCommand](TCommand command) at Kotrak.Common.Infrastructure.Integration.Filters.InboundMessageHandlerFilter.Execute(InternalStorageProcessContext`1 input) at Kotrak.Extensions.Pipeline.Pipeline`1.Execute(T input) at Kotrak.Common.Infrastructure.Integration.Filters.InboundMessagesProcessFilter.Execute(InternalStorageContext`1 input){code}id=53388af5-51f3-4c27-a8cc-5fd65a902392 162713\'", "Comment 4: \' !screenshot-1! !screenshot-2! !screenshot-3! \'", "Comment 5: \' !screenshot-4! !screenshot-5! !screenshot-6! \'", "Comment 6: \'trzymała rezerwacja !screenshot-7! Aktualnie VT jest zamknięty.Rezerwacja była dla VT jeszcze z grudnia 2022.Powiązany DGS-8299teraz jest pobrane x2. !screenshot-9! \'", "Comment 7: \'Hello,I managed to close VT but x2 stocks have been released and they should be restored by inventory.As to the cause", \'Comment 8: in order to determine the cause\', "Comment 9: please accept RCA.\'", "Comment 10: \'Please close this ticket\']"]\nRelated Issues:\n[]\n\n### End'}
340	{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8692\n\n### Instruction:\nHi,\r\n\r\nCan you please explain me how these documents were created. Since the colleague whose name is written at the bottom of the document says that he never created this documents. Is it possible that the system itself creates these documents based on something/what?\n\n### Response:\n["Comment 1: [\'[^IRC.pdf] _(1023 kB)_\'", "Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", \'Comment 3: "Ive checked provided documents and they did not came from DHC. Those documents were created in ERP system by someone who logged into ERPXL through provided operators ID\\\'s: SIMIVLAS andVUKBAR. As I can see those operators do not have password set on their accounts\', \'Comment 4: so anybody who have go t access to ERP system have an ability to create documents in behalf on them.Please\', \'Comment 5: let me know if the answer is sufficient for you. Do you expect any additional actions from us regarding this issue? Can we close this ticket?"\', "Comment 6: \'Hi", \'Comment 7: thank you for the explanation. But still\', \'Comment 8: it is not clear to me why and how these documents were created. Before I sent initial request\', "Comment 9: I already discuss with those colleagues and they claim that nothing is done differently than usual. This correction for certain SOR documents doubled or trippled COGS which made margins wrong. \'", "Comment 10: \'As I wrote earlier", "Comment 11: those documents were created in ERPXL by someone who was logged in asSIMIVLAS or VUKBAR.Anyone who have access to ERP system can log into the system asSIMIVLAS or VUKBAR and create such documents.\'", "Comment 12: \'As I can see in the system logs in February 2023 in ERPXL", \'Comment 13: the VUKBAR operator was logged in by users working on the following domain accounts: VBarjaktarovic\', \'Comment 14: MPETROVIC and ASTAMENKOVIC logged in to the RSTS01 terminal.Please\', "Comment 15: let me know if the answer is sufficient for you. Do you expect any additional actions from us regarding this issue? Can we close this ticket?\'", "Comment 16: \'Please", "Comment 17: let me know if expect any additional actions from us regarding this issue? Can we close this ticket?\'", "Comment 18: \'Please", "Comment 19: let me know if expect any additional actions from us regarding this issue? Can we close this ticket?\'", "Comment 20: \'Not yet please. We just had meeting regarding this and DGS-8653 and we will have to have a video meeting from someone responsible for HelpDesk from KOTRAK to help our management clarify some thing and to se what will we do with that. Thank you for your patience. Best regards.\'", "Comment 21: \'Please", "Comment 22: let me know if expect any additional actions from us regarding this issue? Can we close this ticket?\'", "Comment 23: \'Could you please confirm if we can close this task?Regards\'", "Comment 24: \'Could you please confirm if we can close this task?Regards\']"]\nRelated Issues:\n[]\n\n### End'}
341	{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8691\n\n### Instruction:\nCześć,\r\n\r\nMamy już 2 loty na premixach, gdzie część zarejestrowanych worków nie przechodzi z pcsa do dhp. Temat pilny.\r\n\r\nRafał Boniecki\r\n\r\n\n\n### Response:\n["Comment 1: [\'!image!!image-1!\'", "Comment 2: \'Hello,\\\\r\\\\rWe are investigating your issue. We will inform you about the solution as soon as possible.\\\\r\\\\rRegards\'", "Comment 3: \'Czy mogę poprosić o numer lotów których brakuje?Could you bring missing lot numbers?\'", "Comment 4: \'problem dotyczy lotów 0272060323010 i 0272060323001. Ale chodzi o część niezarejestrowanych worków. Jest w screenach. Same loty przeszły do dhp.\'", "Comment 5: \'to numery z pcs", "Comment 6: z tego o widze w exchange jest takFROM [DH_Exchange].[dbo].[ProductionLotReportHeader] -- order by PLH_Id desc where PLH_LotNumber in ( 0201060323010,0201060323001)\'", "Comment 7: \'select * FROM [DHP_Leczyca].[dbo].[Delivery] where del_plhid in (164739,164755)- brak eanów na delivery\'", "Comment 8: \'!image-2023-03-06-15-59-04-085.png!\'", "Comment 9: \'Kolejny lot z tym błędem: !image-2!\'", "Comment 10: \'!image-3!\'", "Comment 11: \'[[email protected]]dasz radę spojrzeć co się tutaj im zaczęło dziać?\'", "Comment 12: \'[[email protected]] I need to ask our developers for help with that issue.\'", \'Comment 13: "I hope that it won\\\'t take them too much time...."\', "Comment 14: \'!image-2023-03-07-08-20-59-017.png!\'", "Comment 15: \'select* FROM [DHP_Leczyca].[dbo].[RegisterMappings] where rgm_delid in (274375,274409)\'", "Comment 16: \'We managed with this problem", "Comment 17: task to close. Thanks.\']"]\nRelated Issues:\n[]\n\n### End'}
342	{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8690\n\n### Instruction:\nHello,\r\n\r\nthese orders are not in VC-Module, but also I cannot find anything in the error log, so I\'m not sure whats going on and what needs to be done to fix this, please check\n\n### Response:\n["Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", "Comment 2: \'Could you please provide numbers of orders that are missing in VC module?\'", "Comment 3: \'see attached list!afbeelding!\'", "Comment 4: \'select * FROM [DHPlantMaintBusinessLogicMain].[dbo].[Orders] where year =2023 and IsInVehicleControl=0 and month=3select * from OrderExportInfoes where entityid in ( select id from Orders where externalId in (205226,204069,205920,203880,204231,204944,206141,206234,204761,204202,204182,206075,205887,205264))adresy niby sie zgadzajaselect o.id,o.ExternalId,o.MainBusinessPartnerId as partneronorder,o.DocumentNumber,o.ForeignDocumentNumber", "Comment 5: o.MainBusinessPartnerAddressId as addressonorder,a.id as adressid,b.id as bpid from orders o join BusinessPartners b on b.id=o.MainBusinessPartnerIdjoin Addresses a on a.id=b.CurrentAddressIdwhere o. ExternalId in (205226,204069,205920,203880,204231,204944,206141,206234,204761,204202,204182,206075,205887,205264)\'", "Comment 6: \'Hello I resend 13 from 14 salesorder from march 2023", "Comment 7: that were not in VC!image-2023-03-06-15-35-46-185.png\|width=1132,height=227!there were no error message for them.One still hanging.\'", "Comment 8: \'!image-2023-03-06-15-39-42-683.png!\'", "Comment 9: \'w lugu vt jest taki blad przy ponownym przesłaniu\'", "Comment 10: \'Ponowna wysyłka i pomogło wczesniej 2023-03-06 15:38:48 (/Plant.VC.BusinessLogic/DHVD01AP178/14580/48) [Error] Kotrak.Extensions.Pipeline.CatchPipeline - Pipeline execution errorSystem.NullReferenceException: Object reference not set to an instance of an object. at Kotrak.Common.PublishedLanguage.User.Equals(User other) at <>f__AnonymousType0`3.Equals(Object value) at System.Linq.Lookup`2.GetGrouping(TKey key", \'Comment 11: Boolean create) at System.Linq.Lookup`2.Create(IEnumerable`1 source\', \'Comment 12: Func`2 keySelector\', "Comment 13: IEqualityComparer`1 comparer) at System.Linq.GroupedEnumerable`2.GetEnumerator() at Kotrak.Common.Infrastructure.Integration.Filters.InboundMessageAcknowledgeHandlerFilter.Execute(InternalStorageContext`1 input) at Kotrak.Extensions.Pipeline.Pipeline`1.Execute(T input) at Kotrak.Extensions.Pipeline.CatchPipeline`1.Execute(TContext input)błedy jak wyzej\'", "Comment 14: \'please check all order were synchronized to VC module\'", "Comment 15: \'Thanks! any reason why this happened? due to update?\'", "Comment 16: \'Hello", "Comment 17: can you please check location Helmond? Same situation applies there!afbeelding-1!\'", "Comment 18: \'w helmond 12 orderów z marca select*FROM [DHPlantMaintBusinessLogicMain].[dbo].[Orders] where year =2023 and IsInVehicleControl=0 and month=3 and type=2!image-2023-03-07-10-47-18-764.png!\'", "Comment 19: \'Please check now in HelmondIn this task we have focused on clearingandunblocking the process.If there is a need from your sideto investigate the reasonof the issue", \'Comment 20: we may raise RootCause Analysis (RCA)task for you.Please\', "Comment 21: let us knowhow you wish us to proceed.\'", "Comment 22: \'Please create RCA", "Comment 23: then you can close this ticket\'", "Comment 24: \'here is a RCa taskDGS-8703\']"]\nRelated Issues:\n[\'DGS-8703\', \'DAP-13415\']\n\n### End'}
343	{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8689\n\n### Instruction:\nIn MAS BE, the SI\'s based on PI\'s from SR\'s, the sales invoice is hard coded for B005059 De Heus Voeders as supplier. For all customers, we need to use NB as payment method in Intense. This is all right for all customers on the customers, and also for B005059 as you can see in the first screenshot. However, due to the fact that these SI\'s are hard coded, \'Settlement\' keeps on showing as payment method in Intense as you can see in the second screenshot for example (SI-RLB/2023/1301, ID 103103). Can you modify this hard coded scenario and use \'NB\' as payment form Intense?\n\n### Response:\n["Comment 1: [\'!image!!image-1!\'", "Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", \'Comment 3: "Update: because we want to finish this round I manually changed this invoice\\\'s payment method to NB. But I hope you understand my point and you will be able to modify this.!image-2!!image-3!"\', "Comment 4: \'Hello,Do you have an update on this topic?\'", \'Comment 5: "Hi [[email protected]],we\\\'ve made changes in test environment for NB payment form in the SI generation of SR process.You can feel free to test it.Best regards,Grzegorz"\', "Comment 6: \'Zmiany w generacji:Create Sales Invoice (MAS BE) dla Payment Method.\'", "Comment 7: \'My SI automatically went to NB this time", "Comment 8: as we wanted. So this may be implemented in PROD in MAS BE. Thank you Grzegorz!!image-4!\'", "Comment 9: \'[[email protected]],functionality has been moved into prod Intense environment.You can verify it.Best regards,Grzegorz\'", "Comment 10: \'This works now", "Comment 11: thank you!Regards,Steffen\'", \'Comment 12: "Excellent\', \'Comment 13: thank you.I\\\'m closing the task.Best regards,Grzegorz"]\']\nRelated Issues:\n[]\n\n### End'}
344	{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8688\n\n### Instruction:\nThe PCS sent the dosage and lot number, but DHP didn\'t reserved. \r\nItem PSMGC1235, lot number 0851020323023, ingredient 21405, lot number WI-276/2/23, quantity 1 837.555 kg, ingredient in production area.\r\n\r\nCould you check why system didn\'t reserved the quantity?\r\n\r\nThank you\n\n### Response:\n["Comment 1: [\'!image!!image-1!!image-2!\'", "Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", "Comment 3: \'Hello,\\\\r\\\\rWe are investigating your issue. We will inform you about the solution as soon as possible.\\\\r\\\\rRegards\\\\r\\\\r\'", "Comment 4: \'Could you please provide new password for my user for mubrasil domain?mubrasil\\\\\\\\ajanuszewska\'", "Comment 5: \'new password 123Change\'", "Comment 6: \'plr id=7c43f146-594f-420e-8772-1e5055822\'", \'Comment 7: "brak stockunitidSELECT TOP (1000) [Id] ,[No] ,[ItemId] ,[DeliveryId] ,[StockUnitId] ,[Quantity] ,[QuantityUnit] FROM [DHPlantStockBusinessLogicMain].[dbo].[ProductionLotReservations] where id=\\\'7C43F146-594F-420E-8772-1E5055822DCB\\\' and ItemId =\\\'BBFEEAD7-6160-4DBA-A768-76572A4991F5\\\'"\', \'Comment 8: "select* FROM [DHPlantStockBusinessLogicMain].[dbo].[StockUnits] where DeliveryId=\\\'90907450-9EE3-48FC-BBDA-BA0B3E6A6EF3\\\' and itemid=\\\'BBFEEAD7-6160-4DBA-A768-76572A4991F5\\\'!image-2023-03-07-09-41-57-320.png!"\', \'Comment 9: "Jak wyżej w modul stock tabelaFROM[DHPlantStockBusinessLogicMain].[dbo].[ProductionLotReservations]where id=\\\'7C43F146-594F-420E-8772-1E5055822DCB\\\'and ItemId =\\\'BBFEEAD7-6160-4DBA-A768-76572A4991F5\\\'brak stockunitid dla podanego itemuporownujac quantityonhand dla stockunitachmamy SELECT ST.ID,W.ID,W.LogisticStatus,ST.BARCODE,ST.Quantity,ST.QuantityOnHand,ST.QuantityUnit\', \'Comment 10: ST.QuantityOnHandUnit\', "Comment 11: W.LogisticStatus,W.QuantityOnHandUnit,W.QuantityOnHandValue ,W.ReservedQuantityUnit,W.ReservedQuantityValue FROM [DHPlantStockBusinessLogicMain].[dbo].[StockUnits] ST JOIN [DHPlantWmsBusinessLogicMain].[dbo].[StockUnits] W ON ST.ID=W.ID where ST.DeliveryId=\'90907450-9EE3-48FC-BBDA-BA0B3E6A6EF3\'mamy dla 2 pozycji qunatotyon hand tyle że + - pokrywa to rezerwacje.pytanie jak to poprawić SELECT ST.ID,W.ID,W.LogisticStatus,ST.BARCODE,ST.Quantity,ST.QuantityOnHand,ST.QuantityUnit", \'Comment 12: ST.QuantityOnHandUnit\', \'Comment 13: W.LogisticStatus,W.QuantityOnHandUnit,W.QuantityOnHandValue ,W.ReservedQuantityUnit,W.ReservedQuantityValue FROM [DHPlantStockBusinessLogicMain].[dbo].[StockUnits] ST JOIN [DHPlantWmsBusinessLogicMain].[dbo].[StockUnits] W ON ST.ID=W.ID where ST.DeliveryId=\\\'90907450-9EE3-48FC-BBDA-BA0B3E6A6EF3\\\'!image-2023-03-07-10-02-24-944.png!"\', "Comment 14: \'[[email protected]] a nie macie skryptów do poprawy tego?\'", "Comment 15: \'Aktualnie brak wyników!image-2023-04-18-18-30-36-036.png!\'", "Comment 16: \'Could you verify if stocks are now ok", "Comment 17: may we close the task ?Did you have any more similar cases?\']"]\nRelated Issues:\n[]\n\n### End'}
345	{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8687\n\n### Instruction:\nHello,\r\n\r\nP1 issue! An order is send tp pcs Ravenstein, I can find the message in the requestlog, see attached.\r\n\r\nHowever, the order is NOT visible in DHP, also not in masterdata. This should be impossible, please check whats going on ASAP. SO number = SO000075533\n\n### Response:\n["Comment 1: [\'[^SOSO000075533.json] _(4 kB)_\'", "Comment 2: \'Hello,\\\\r\\\\rWe are investigating your issue. We will inform you about the solution as soon as possible.\\\\r\\\\rRegards\\\\r\\\\r\'", "Comment 3: \'Order nie wpadł tylko do modułu VC. W logach VC z dnia 28.02 pojawiały się informacje o problemach z rabbitem. Po ponownym przesynchronizowaniu ordera wpadł od do VC. Resendowałam też Tripa", "Comment 4: bo nie wpadł przez brak tego SO.!ORDER_ASN!\'", "Comment 5: \'Dear Thomas,Order is in DHP but not in VC module:!image-2023-03-06-12-35-03-459.png!There is a mess with addresses again. I hope", "Comment 6: I have marked it legibly. So>> in yellow we have main business and payer Business Partner>> but they have assigned the address id that belongs to Target Business Partner>> please ask Milas to correct it and resend the questioned Order.!image-2023-03-06-12-34-45-657.png!Regards\'", \'Comment 7: "Hi Aleksandra: Oke good to know\', "Comment 8: because this I know how to fix :) So I\'m relieved", \'Comment 9: I did not see the order in the masterdata of DHP\', \'Comment 10: so that\\\'s why I was confused. Do you know why it\\\'s not visible there?"\', \'Comment 11: "Dev Team also reported some issues with Rabbit on 28th of February. They have resynced Order and resent Trip because it was also missing. Please check now. So to be honest now I\\\'m not sure if this is address issue or Rabbit issue. However\', \'Comment 12: there is some mess with addresses still...Regards"\', "Comment 13: \'Hi,I think we can treat this issue now as incidental case. Can we close this task?Regards\'", "Comment 14: \'Ticket can be closed\'", "Comment 15: \'Thank you\']"]\nRelated Issues:\n[]\n\n### End'}
346	{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8686\n\n### Instruction:\nHello, \r\n\r\nlot report 0061270123041 is in status \'in progress\'. But there are two batches missing. I found those in the APIrequest log, but when I try to reprocess those, I got the message that the lot is already finished. The 2 missing batchreport xmls are added to the ticket. Can you investigate and make sure these are registered correctly? because produced quantity is not send to ERP and is leading to problems.\n\n### Response:\n["Comment 1: [\'Hello,We are investigating your issue.Please be informed that we have forwarded the issue to the development team in order to internal analysis.We are waiting for more details and will be back with further information as soon as possible.Regards\'", "Comment 2: \'PLR has been already confirmed and synchronized to ERP:!image-2023-04-20-13-35-41-414!The batches whose XML files were attached to the task were registered:!image-2023-04-20-13-39-38-210![[email protected]]please confirm if the issue is still valid? (PLR was registered in January - we do not have logs from this period to determine why the batches were not registered)\'", "Comment 3: \'Dzięki Wojtek\'", "Comment 4: \'Hi,PLR has been already confirmed and synchronized to ERP:!image-2023-04-20-13-48-58-728.png\|width=1092,height=528!The batches whose XML files were attached to the task were registered:!image-2023-04-20-13-49-20-439.png\|width=1119,height=254!Please", "Comment 5: let us know if this is fine for you.Regards\']"]\nRelated Issues:\n[\'DGS-8443\', \'DGS-8604\']\n\n### End'}
347	{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8685\n\n### Instruction:\nHi\r\nPlease help to check this case .\r\nCan\'t create Production order for item 66CC-43++-F-B25 with erros messege is "No bags found for item66CC-43++-F-B25 ".\r\nChecked the recipe and item packaging (BPEC01170) are no problem.\n\n### Response:\n["Comment 1: [\'!image!\'", "Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", \'Comment 3: "Hello,Sorry\', \'Comment 4: but I\\\'m having a problem connecting.\|115.75.177.45:3382\|Regards"\', "Comment 5: \'We are checking", "Comment 6: the connection works.\'", "Comment 7: \'What user name are you logging in with?\'", \'Comment 8: " !screenshot-1! {code:java} FROM [DHPlantProdBusinessLogicMain].[dbo].[Items] where code like \\\'66CC-43++-F%\\\'{code}!image-2023-03-06-08-55-17-535!"\', "Comment 9: \'The item has been resent from DHC", "Comment 10: can you check again?\'", "Comment 11: \'Thanks u. Production order for this item already be created.U can close this ticket.\'", "Comment 12: \'Thank you for confirmation.\']"]\nRelated Issues:\n[]\n\n### End'}
348	{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8684\n\n### Instruction:\nPro from 104 to 117 missing from exchange.\r\n\n\n### Response:\n["Comment 1: [\'!image!!image-1!\'", "Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", \'Comment 3: "I use this to check for missing items\', \'Comment 4: recipes\', \'Comment 5: orders\', \'Comment 6: and partners linked to a ProSELECT top 100 mpr.DocumentNumber as [Prod.PRP] \', \'Comment 7: mpr.CreateDate as [Prod.Created] \', "Comment 8: case when pri.import is null then \'MISSING\' else \'Imported\' end as PCS_Production_Request ", "Comment 9: case rci.import when null then mrc.Name else \'Imported\' end as PCS_Recipe ", "Comment 10: case when ord.import is null then mor.FullDocumentNumber else \'Imported\' end as PCS_SO ", "Comment 11: case iti.import when 0 then mit.Code else \'Imported\' end as PCS_Item ", \'Comment 12: case when bpi.import = 0 then \\\'Imported\\\' else mbp.Code end as PCS_Partner FROM [DHPlantProdBusinessLogicMain].[dbo].[ProductionOrders] mpr LEFT JOIN [DHPlantProdBusinessLogicMain].[dbo].ProductionOrderOrderElements mpo ON mpo.id = mpr.Id LEFT JOIN [DHPlantProdBusinessLogicMain].[dbo].Items mit ON mit.Id = mpr.ReadyProductId LEFT JOIN [DHPlantProdBusinessLogicMain].[dbo].BusinessPartners mbp ON mbp.id = mpr.BusinessPartnerId LEFT JOIN [DHPlantProdBusinessLogicMain].[dbo].Orders mor ON mor.id = mpo.OrderId LEFT JOIN [DHPlantProdBusinessLogicMain].[dbo].Recipes mrc ON mrc.id = mpr.RecipeId --Produciton Order left join [10.0.23.10].[DHExchange67].[dbo].[ProductionOrders] pro on pro.id = mpr.id left join [10.0.23.10].[DHExchange67].[api].[ProductionOrdersImport] pri on pro.entityid = pri.id --Recipes left join [10.0.23.10].[DHExchange67].[dbo].[Recipes] rch on rch.id = mpr.RecipeId left join [10.0.23.10].[DHExchange67].[api].[RecipesImport] rci on rci.id = rch.[EntityId] --Order left join [10.0.23.10].[DHExchange67].[dbo].[Orders] orh ON orh.id = mpo.orderid left join [10.0.23.10].[DHExchange67].[api].[OrdersImport] ord ON ord.id = orh.entityid --Item left join [10.0.23.10].[DHExchange67].[dbo].Items itm ON itm.id = mpr.ReadyProductId LEFT JOIN [10.0.23.10].[DHExchange67].api.ItemsImport iti ON iti.id = itm.entityid --Partner LEFT JOIN [10.0.23.10].[DHExchange67].[dbo].[BusinessPartners] bpt ON bpt.id = mpr.BusinessPartnerId LEFT JOIN [10.0.23.10].[DHExchange67].[api].[BusinessPartnersImport] bpi ON bpi.id = bpt.entityid\\\\t where pri.id is null order by mpr.createdate descplease tell me if something else is blocking or missing that stops them from going through."\', "Comment 13: \'Wszystkie PrO są z 5 marca", \'Comment 14: ostatni host log w tym dniu:{code:java}2023-03-05 13:51:33 (/Plant.PCS.BusinessLogic/SAKDSRV04/18088/1) [Fatal] Microsoft.AspNetCore.Hosting.Diagnostics - Application startup exceptionAutofac.Core.DependencyResolutionException: An exception was thrown while activating λ:Kotrak.Integration.IntegrationPluginCommon.MessageHandling.IIntercontextCommunicationSubscription[] -> Plant.PCS.BusinessLogic.Infrastructure.ContextIntegration.Subscriptions.WMS.WarehouseOrderElementReadyToProcess.WarehouseOrderElementReadyToProcessMessageSubscription -> Kotrak.Integration.RabbitMQClient.MessageBusClient -> RawRabbit.BusClient -> λ:RawRabbit.Channel.Abstraction.IChannelFactory. ---> RabbitMQ.Client.Exceptions.BrokerUnreachableException: None of the specified endpoints were reachable ---> RabbitMQ.Client.Exceptions.PossibleAuthenticationFailureException: Possibly caused by authentication failure ---> RabbitMQ.Client.Exceptions.OperationInterruptedException: The AMQP operation was interrupted: AMQP close-reason\', \'Comment 15: initiated by Library\', \'Comment 16: code=541\', \'Comment 17: text="Unexpected Exception"\', \'Comment 18: classId=0\', \'Comment 19: methodId=0\', \'Comment 20: cause=System.IO.IOException: Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host.. ---> System.Net.Sockets.SocketException (10054): An existing connection was forcibly closed by the remote host. at System.Net.Sockets.NetworkStream.Read(Byte[] buffer\', \'Comment 21: Int32 offset\', \'Comment 22: Int32 count) --- End of inner exception stack trace --- at RabbitMQ.Client.Impl.Frame.ReadFrom(NetworkBinaryReader reader) at RabbitMQ.Client.Impl.SocketFrameHandler.ReadFrame() at RabbitMQ.Client.Framing.Impl.Connection.MainLoopIteration() at RabbitMQ.Client.Framing.Impl.Connection.MainLoop() at RabbitMQ.Client.Impl.SimpleBlockingRpcContinuation.GetReply(TimeSpan timeout) at RabbitMQ.Client.Impl.ModelBase.ConnectionStartOk(IDictionary`2 clientProperties\', \'Comment 23: String mechanism\', \'Comment 24: Byte[] response\', \'Comment 25: String locale) at RabbitMQ.Client.Framing.Impl.Connection.StartAndTune() --- End of inner exception stack trace --- at RabbitMQ.Client.Framing.Impl.Connection.StartAndTune() at RabbitMQ.Client.Framing.Impl.Connection.Open(Boolean insist) at RabbitMQ.Client.Framing.Impl.Connection..ctor(IConnectionFactory factory\', \'Comment 26: Boolean insist\', \'Comment 27: IFrameHandler frameHandler\', \'Comment 28: String clientProvidedName) at RabbitMQ.Client.Framing.Impl.AutorecoveringConnection.Init(IFrameHandler fh) at RabbitMQ.Client.Framing.Impl.AutorecoveringConnection.Init(IEndpointResolver endpoints) at RabbitMQ.Client.ConnectionFactory.CreateConnection(IEndpointResolver endpointResolver\', \'Comment 29: String clientProvidedName) --- End of inner exception stack trace --- at RabbitMQ.Client.ConnectionFactory.CreateConnection(IEndpointResolver endpointResolver\', \'Comment 30: String clientProvidedName) at RabbitMQ.Client.ConnectionFactory.CreateConnection(IList`1 hostnames\', \'Comment 31: String clientProvidedName) at RabbitMQ.Client.ConnectionFactory.CreateConnection(IList`1 hostnames) at RawRabbit.Channel.ChannelFactory.ConnectAsync(CancellationToken token) at RawRabbit.DependencyInjection.RawRabbitDependencyRegisterExtension.<>c.<AddRawRabbit>b__0_3(IDependencyResolver resolver) at RawRabbit.DependencyInjection.Autofac.ContainerBuilderAdapter.<>c__DisplayClass5_0`2.<AddSingleton>b__0(IComponentContext context) at Autofac.Builder.RegistrationBuilder.<>c__DisplayClass0_0`1.<ForDelegate>b__0(IComponentContext c\', \'Comment 32: IEnumerable`1 p) at Autofac.Core.Activators.Delegate.DelegateActivator.ActivateInstance(IComponentContext context\', \'Comment 33: IEnumerable`1 parameters) at Autofac.Core.Resolving.InstanceLookup.Activate(IEnumerable`1 parameters\', \'Comment 34: Object& decoratorTarget) --- End of inner exception stack trace --- at Autofac.Core.Resolving.InstanceLookup.Activate(IEnumerable`1 parameters\', \'Comment 35: Object& decoratorTarget) at Autofac.Core.Resolving.InstanceLookup.Execute() at Autofac.Core.Resolving.ResolveOperation.GetOrCreateInstance(ISharingLifetimeScope currentOperationScope\', \'Comment 36: IComponentRegistration registration\', \'Comment 37: IEnumerable`1 parameters) at Autofac.Core.Resolving.ResolveOperation.Execute(IComponentRegistration registration\', \'Comment 38: IEnumerable`1 parameters) at Autofac.ResolutionExtensions.TryResolveService(IComponentContext context\', \'Comment 39: Service service\', \'Comment 40: IEnumerable`1 parameters\', \'Comment 41: Object& instance) at Autofac.ResolutionExtensions.ResolveService(IComponentContext context\', \'Comment 42: Service service\', \'Comment 43: IEnumerable`1 parameters) at Autofac.ResolutionExtensions.Resolve(IComponentContext context\', \'Comment 44: Type serviceType) at Autofac.Extensions.DependencyInjection.AutofacServiceProvider.GetRequiredService(Type serviceType) at Microsoft.Extensions.DependencyInjection.ServiceProviderServiceExtensions.GetRequiredService[T](IServiceProvider provider) at Microsoft.Extensions.DependencyInjection.ServiceProviderServiceExtensions.GetServices[T](IServiceProvider provider) at Kotrak.Common.Infrastructure.Hosting.Extensions.ApplicationBuilderExtensions.UserIntercontextCommunicationSubscriptions(IApplicationBuilder builder) at Kotrak.Common.Infrastructure.Hosting.CommonStartup`2.Configure(IApplicationBuilder app\', \'Comment 45: IHostApplicationLifetime applicationLifetime) at Plant.PCS.BusinessLogic.Infrastructure.Startup.Configure(IApplicationBuilder app\', \'Comment 46: IHostApplicationLifetime applicationLifetime) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\9ecc36be9059f942\\\\\\\\Plant.PCS.BusinessLogic\\\\\\\\Infrastructure\\\\\\\\Startup.cs:line 25 at System.RuntimeMethodHandle.InvokeMethod(Object target\', \'Comment 47: Span`1& arguments\', \'Comment 48: Signature sig\', \'Comment 49: Boolean constructor\', \'Comment 50: Boolean wrapExceptions) at System.Reflection.RuntimeMethodInfo.Invoke(Object obj\', \'Comment 51: BindingFlags invokeAttr\', \'Comment 52: Binder binder\', \'Comment 53: Object[] parameters\', \'Comment 54: CultureInfo culture) at Microsoft.AspNetCore.Hosting.ConfigureBuilder.Invoke(Object instance\', "Comment 55: IApplicationBuilder builder) at Microsoft.AspNetCore.Hosting.ConfigureBuilder.<>c__DisplayClass4_0.<Build>b__0(IApplicationBuilder builder) at Microsoft.AspNetCore.Hosting.GenericWebHostBuilder.<>c__DisplayClass15_0.<UseStartup>b__1(IApplicationBuilder app) at Microsoft.AspNetCore.Mvc.Filters.MiddlewareFilterBuilderStartupFilter.<>c__DisplayClass0_0.<Configure>g__MiddlewareFilterBuilder\|0(IApplicationBuilder builder) at Microsoft.AspNetCore.Server.IIS.Core.IISServerSetupFilter.<>c__DisplayClass2_0.<Configure>b__0(IApplicationBuilder app) at Microsoft.AspNetCore.HostFilteringStartupFilter.<>c__DisplayClass0_0.<Configure>b__0(IApplicationBuilder app) at Microsoft.AspNetCore.Hosting.GenericWebHostService.StartAsync(CancellationToken cancellationToken){code}\'", "Comment 56: \'Log log{code:java}2023-03-05 13:51:19 (/Plant.PCS.BusinessLogic/SAKDSRV04/18088/1) [Error] Kotrak.Common.Infrastructure.Hosting.BaseStartup - An error occurred while seeding the database.Microsoft.Data.SqlClient.SqlException (0x80131904): A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider", \'Comment 57: error: 40 - Could not open a connection to SQL Server) ---> System.ComponentModel.Win32Exception (53): The network path was not found. at Microsoft.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception\', \'Comment 58: Boolean breakConnection\', \'Comment 59: Action`1 wrapCloseInAction) at Microsoft.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj\', \'Comment 60: Boolean callerHasConnectionLock\', \'Comment 61: Boolean asyncClose) at Microsoft.Data.SqlClient.TdsParser.Connect(ServerInfo serverInfo\', \'Comment 62: SqlInternalConnectionTds connHandler\', \'Comment 63: Boolean ignoreSniOpenTimeout\', \'Comment 64: Int64 timerExpire\', \'Comment 65: Boolean encrypt\', \'Comment 66: Boolean trustServerCert\', \'Comment 67: Boolean integratedSecurity\', \'Comment 68: Boolean withFailover\', \'Comment 69: SqlAuthenticationMethod authType) at Microsoft.Data.SqlClient.SqlInternalConnectionTds.AttemptOneLogin(ServerInfo serverInfo\', \'Comment 70: String newPassword\', \'Comment 71: SecureString newSecurePassword\', \'Comment 72: Boolean ignoreSniOpenTimeout\', \'Comment 73: TimeoutTimer timeout\', \'Comment 74: Boolean withFailover) at Microsoft.Data.SqlClient.SqlInternalConnectionTds.LoginNoFailover(ServerInfo serverInfo\', \'Comment 75: String newPassword\', \'Comment 76: SecureString newSecurePassword\', \'Comment 77: Boolean redirectedUserInstance\', \'Comment 78: SqlConnectionString connectionOptions\', \'Comment 79: SqlCredential credential\', \'Comment 80: TimeoutTimer timeout) at Microsoft.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(TimeoutTimer timeout\', \'Comment 81: SqlConnectionString connectionOptions\', \'Comment 82: SqlCredential credential\', \'Comment 83: String newPassword\', \'Comment 84: SecureString newSecurePassword\', \'Comment 85: Boolean redirectedUserInstance) at Microsoft.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity\', \'Comment 86: SqlConnectionString connectionOptions\', \'Comment 87: SqlCredential credential\', \'Comment 88: Object providerInfo\', \'Comment 89: String newPassword\', \'Comment 90: SecureString newSecurePassword\', \'Comment 91: Boolean redirectedUserInstance\', \'Comment 92: SqlConnectionString userConnectionOptions\', \'Comment 93: SessionData reconnectSessionData\', \'Comment 94: Boolean applyTransientFaultHandling\', \'Comment 95: String accessToken\', \'Comment 96: DbConnectionPool pool) at Microsoft.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options\', \'Comment 97: DbConnectionPoolKey poolKey\', \'Comment 98: Object poolGroupProviderInfo\', \'Comment 99: DbConnectionPool pool\', \'Comment 100: DbConnection owningConnection\', \'Comment 101: DbConnectionOptions userOptions) at Microsoft.Data.ProviderBase.DbConnectionFactory.CreatePooledConnection(DbConnectionPool pool\', \'Comment 102: DbConnection owningObject\', \'Comment 103: DbConnectionOptions options\', \'Comment 104: DbConnectionPoolKey poolKey\', \'Comment 105: DbConnectionOptions userOptions) at Microsoft.Data.ProviderBase.DbConnectionPool.CreateObject(DbConnection owningObject\', \'Comment 106: DbConnectionOptions userOptions\', \'Comment 107: DbConnectionInternal oldConnection) at Microsoft.Data.ProviderBase.DbConnectionPool.UserCreateRequest(DbConnection owningObject\', \'Comment 108: DbConnectionOptions userOptions\', \'Comment 109: DbConnectionInternal oldConnection) at Microsoft.Data.ProviderBase.DbConnectionPool.TryGetConnection(DbConnection owningObject\', \'Comment 110: UInt32 waitForMultipleObjectsTimeout\', \'Comment 111: Boolean allowCreate\', \'Comment 112: Boolean onlyOneCheckConnection\', \'Comment 113: DbConnectionOptions userOptions\', \'Comment 114: DbConnectionInternal& connection) at Microsoft.Data.ProviderBase.DbConnectionPool.TryGetConnection(DbConnection owningObject\', \'Comment 115: TaskCompletionSource`1 retry\', \'Comment 116: DbConnectionOptions userOptions\', \'Comment 117: DbConnectionInternal& connection) at Microsoft.Data.ProviderBase.DbConnectionFactory.TryGetConnection(DbConnection owningConnection\', \'Comment 118: TaskCompletionSource`1 retry\', \'Comment 119: DbConnectionOptions userOptions\', \'Comment 120: DbConnectionInternal oldConnection\', \'Comment 121: DbConnectionInternal& connection) at Microsoft.Data.ProviderBase.DbConnectionInternal.TryOpenConnectionInternal(DbConnection outerConnection\', \'Comment 122: DbConnectionFactory connectionFactory\', \'Comment 123: TaskCompletionSource`1 retry\', \'Comment 124: DbConnectionOptions userOptions) at Microsoft.Data.ProviderBase.DbConnectionClosed.TryOpenConnection(DbConnection outerConnection\', \'Comment 125: DbConnectionFactory connectionFactory\', \'Comment 126: TaskCompletionSource`1 retry\', \'Comment 127: DbConnectionOptions userOptions) at Microsoft.Data.SqlClient.SqlConnection.TryOpen(TaskCompletionSource`1 retry\', \'Comment 128: SqlConnectionOverrides overrides) at Microsoft.Data.SqlClient.SqlConnection.Open(SqlConnectionOverrides overrides) at Microsoft.EntityFrameworkCore.SqlServer.Storage.Internal.SqlServerConnection.OpenDbConnection(Boolean errorsExpected) at Microsoft.EntityFrameworkCore.Storage.RelationalConnection.OpenInternal(Boolean errorsExpected) at Microsoft.EntityFrameworkCore.Storage.RelationalConnection.Open(Boolean errorsExpected) at Microsoft.EntityFrameworkCore.SqlServer.Storage.Internal.SqlServerDatabaseCreator.<>c__DisplayClass18_0.<Exists>b__0(DateTime giveUp) at Microsoft.EntityFrameworkCore.ExecutionStrategyExtensions.<>c__DisplayClass12_0`2.<Execute>b__0(DbContext c\', \'Comment 129: TState s) at Microsoft.EntityFrameworkCore.SqlServer.Storage.Internal.SqlServerExecutionStrategy.Execute[TState,TResult](TState state\', \'Comment 130: Func`3 operation\', \'Comment 131: Func`3 verifySucceeded) at Microsoft.EntityFrameworkCore.ExecutionStrategyExtensions.Execute[TState,TResult](IExecutionStrategy strategy\', \'Comment 132: TState state\', \'Comment 133: Func`2 operation\', "Comment 134: Func`2 verifySucceeded) at Microsoft.EntityFrameworkCore.SqlServer.Storage.Internal.SqlServerDatabaseCreator.Exists(Boolean retryOnNotExists) at Microsoft.EntityFrameworkCore.SqlServer.Storage.Internal.SqlServerDatabaseCreator.Exists() at Microsoft.EntityFrameworkCore.Migrations.HistoryRepository.Exists() at Microsoft.EntityFrameworkCore.Migrations.Internal.Migrator.Migrate(String targetMigration) at Microsoft.EntityFrameworkCore.RelationalDatabaseFacadeExtensions.Migrate(DatabaseFacade databaseFacade) at Kotrak.Common.Infrastructure.EF.DbInitializer.Init() at Kotrak.Common.Infrastructure.Hosting.CommonStartup`1.OnSeedDatabase(IServiceProvider services) at Kotrak.Common.Infrastructure.Hosting.CommonStartup`2.OnSeedDatabase(IServiceProvider services) at Kotrak.Common.Infrastructure.Hosting.CommonStartup`3.OnSeedDatabase(IServiceProvider services) at Kotrak.Common.Infrastructure.Hosting.BaseStartup.SeedDatabase(IApplicationBuilder builder)ClientConnectionId:00000000-0000-0000-0000-000000000000Error Number:53,State:0,Class:20{code}\'", \'Comment 135: "W ogóle to są ostatnie logi :D{code:java}2023-03-05 13:48:45 (/Plant.PCS.BusinessLogic/SAKDSRV04/5104/128) [Error] Kotrak.Integration.InternalStorage.IInternalStorageRepository - Error during System.Collections.Generic.IReadOnlyCollection`1[Kotrak.Integration.InternalStorage.EF.Entities.InboundEntity] Get(Int32) methodSystem.ObjectDisposedException: Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \\\'Dispose\\\' on the context instance\', \'Comment 136: or wrapping it in a using statement. If you are using dependency injection\', "Comment 137: you should let the dependency injection container take care of disposing context instances.Object name: \'IntercontextCommunicationDbContext\'. at Microsoft.EntityFrameworkCore.DbContext.CheckDisposed() at Microsoft.EntityFrameworkCore.DbContext.get_ContextServices() at Microsoft.EntityFrameworkCore.DbContext.get_ChangeTracker() at Microsoft.EntityFrameworkCore.Query.CompiledQueryCacheKeyGenerator.GenerateCacheKeyCore(Expression query", \'Comment 138: Boolean async) at Microsoft.EntityFrameworkCore.Query.RelationalCompiledQueryCacheKeyGenerator.GenerateCacheKeyCore(Expression query\', \'Comment 139: Boolean async) at Microsoft.EntityFrameworkCore.SqlServer.Query.Internal.SqlServerCompiledQueryCacheKeyGenerator.GenerateCacheKey(Expression query\', "Comment 140: Boolean async) at Microsoft.EntityFrameworkCore.Query.Internal.QueryCompiler.Execute[TResult](Expression query) at Microsoft.EntityFrameworkCore.Query.Internal.EntityQueryable`1.GetEnumerator() at System.Collections.Generic.List`1..ctor(IEnumerable`1 collection) at System.Linq.Enumerable.ToList[TSource](IEnumerable`1 source) at Castle.Proxies.Invocations.IInternalStorageRepository`1_Get_8.InvokeMethodOnTarget() at Castle.DynamicProxy.AbstractInvocation.Proceed() at Kotrak.Common.Infrastructure.Interceptors.LoggingInterceptor`1.Intercept(IInvocation invocation)2023-03-05 13:48:45 (/Plant.PCS.BusinessLogic/SAKDSRV04/5104/128) [Error] Kotrak.Integration.InternalStorage.IInternalStorageRepository - Error during System.Collections.Generic.IReadOnlyCollection`1[Kotrak.Integration.InternalStorage.EF.Entities.InboundEntity] Get(Int32) methodSystem.ObjectDisposedException: Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance", \'Comment 141: or wrapping it in a using statement. If you are using dependency injection\', "Comment 142: you should let the dependency injection container take care of disposing context instances.Object name: \'IntercontextCommunicationDbContext\'. at Microsoft.EntityFrameworkCore.DbContext.CheckDisposed() at Microsoft.EntityFrameworkCore.DbContext.get_ContextServices() at Microsoft.EntityFrameworkCore.DbContext.get_ChangeTracker() at Microsoft.EntityFrameworkCore.Query.CompiledQueryCacheKeyGenerator.GenerateCacheKeyCore(Expression query", \'Comment 143: Boolean async) at Microsoft.EntityFrameworkCore.Query.RelationalCompiledQueryCacheKeyGenerator.GenerateCacheKeyCore(Expression query\', \'Comment 144: Boolean async) at Microsoft.EntityFrameworkCore.SqlServer.Query.Internal.SqlServerCompiledQueryCacheKeyGenerator.GenerateCacheKey(Expression query\', \'Comment 145: Boolean async) at Microsoft.EntityFrameworkCore.Query.Internal.QueryCompiler.Execute[TResult](Expression query) at Microsoft.EntityFrameworkCore.Query.Internal.EntityQueryable`1.GetEnumerator() at System.Collections.Generic.List`1..ctor(IEnumerable`1 collection) at System.Linq.Enumerable.ToList[TSource](IEnumerable`1 source) at Castle.Proxies.Invocations.IInternalStorageRepository`1_Get_8.InvokeMethodOnTarget() at Castle.DynamicProxy.AbstractInvocation.Proceed() at Kotrak.Common.Infrastructure.Interceptors.LoggingInterceptor`1.Intercept(IInvocation invocation){code}"\', \'Comment 146: \\\'Druga linia nie odp!image-2023-03-05-18-59-23-028.png!{code:java}2023-03-04 15:26:19 (/Plant.PCS.BusinessLogic2/SAKDSRV04/13660/202) [Error] Microsoft.EntityFrameworkCore.Database.Connection - An error occurred using the connection to database \\\\\\\'"DHExchange70"\\\\\\\' on server \\\\\\\'"10.0.23.10"\\\\\\\'.2023-03-04 15:26:19 (/Plant.PCS.BusinessLogic2/SAKDSRV04/13660/202) [Error] Microsoft.EntityFrameworkCore.Query - An exception occurred while iterating over the results of a query for context type \\\\\\\'"Plant.PCS.BusinessLogic.Infrastructure.EF.PcsDbContext"\\\\\\\'."""Microsoft.Data.SqlClient.SqlException (0x80131904): A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider\', \'Comment 147: error: 40 - Could not open a connection to SQL Server) ---> System.ComponentModel.Win32Exception (53): The network path was not found. at Microsoft.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj\', \'Comment 148: Boolean callerHasConnectionLock\', \'Comment 149: Boolean asyncClose) at Microsoft.Data.SqlClient.TdsParser.Connect(ServerInfo serverInfo\', \'Comment 150: SqlInternalConnectionTds connHandler\', \'Comment 151: Boolean ignoreSniOpenTimeout\', \'Comment 152: Int64 timerExpire\', \'Comment 153: Boolean encrypt\', \'Comment 154: Boolean trustServerCert\', \'Comment 155: Boolean integratedSecurity\', \'Comment 156: Boolean withFailover\', \'Comment 157: SqlAuthenticationMethod authType) at Microsoft.Data.SqlClient.SqlInternalConnectionTds.AttemptOneLogin(ServerInfo serverInfo\', \'Comment 158: String newPassword\', \'Comment 159: SecureString newSecurePassword\', \'Comment 160: Boolean ignoreSniOpenTimeout\', \'Comment 161: TimeoutTimer timeout\', \'Comment 162: Boolean withFailover) at Microsoft.Data.SqlClient.SqlInternalConnectionTds.LoginNoFailover(ServerInfo serverInfo\', \'Comment 163: String newPassword\', \'Comment 164: SecureString newSecurePassword\', \'Comment 165: Boolean redirectedUserInstance\', \'Comment 166: SqlConnectionString connectionOptions\', \'Comment 167: SqlCredential credential\', \'Comment 168: TimeoutTimer timeout) at Microsoft.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(TimeoutTimer timeout\', \'Comment 169: SqlConnectionString connectionOptions\', \'Comment 170: SqlCredential credential\', \'Comment 171: String newPassword\', \'Comment 172: SecureString newSecurePassword\', \'Comment 173: Boolean redirectedUserInstance) at Microsoft.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity\', \'Comment 174: SqlConnectionString connectionOptions\', \'Comment 175: SqlCredential credential\', \'Comment 176: Object providerInfo\', \'Comment 177: String newPassword\', \'Comment 178: SecureString newSecurePassword\', \'Comment 179: Boolean redirectedUserInstance\', \'Comment 180: SqlConnectionString userConnectionOptions\', \'Comment 181: SessionData reconnectSessionData\', \'Comment 182: Boolean applyTransientFaultHandling\', \'Comment 183: String accessToken\', \'Comment 184: DbConnectionPool pool) at Microsoft.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options\', \'Comment 185: DbConnectionPoolKey poolKey\', \'Comment 186: Object poolGroupProviderInfo\', \'Comment 187: DbConnectionPool pool\', \'Comment 188: DbConnection owningConnection\', \'Comment 189: DbConnectionOptions userOptions) at Microsoft.Data.ProviderBase.DbConnectionFactory.CreatePooledConnection(DbConnectionPool pool\', \'Comment 190: DbConnection owningObject\', \'Comment 191: DbConnectionOptions options\', \'Comment 192: DbConnectionPoolKey poolKey\', \'Comment 193: DbConnectionOptions userOptions) at Microsoft.Data.ProviderBase.DbConnectionPool.CreateObject(DbConnection owningObject\', \'Comment 194: DbConnectionOptions userOptions\', \'Comment 195: DbConnectionInternal oldConnection) at Microsoft.Data.ProviderBase.DbConnectionPool.UserCreateRequest(DbConnection owningObject\', \'Comment 196: DbConnectionOptions userOptions\', \'Comment 197: DbConnectionInternal oldConnection) at Microsoft.Data.ProviderBase.DbConnectionPool.TryGetConnection(DbConnection owningObject\', \'Comment 198: UInt32 waitForMultipleObjectsTimeout\', \'Comment 199: Boolean allowCreate\', \'Comment 200: Boolean onlyOneCheckConnection\', \'Comment 201: DbConnectionOptions userOptions\', \'Comment 202: DbConnectionInternal& connection) at Microsoft.Data.ProviderBase.DbConnectionPool.TryGetConnection(DbConnection owningObject\', \'Comment 203: TaskCompletionSource`1 retry\', \'Comment 204: DbConnectionOptions userOptions\', \'Comment 205: DbConnectionInternal& connection) at Microsoft.Data.ProviderBase.DbConnectionFactory.TryGetConnection(DbConnection owningConnection\', \'Comment 206: TaskCompletionSource`1 retry\', \'Comment 207: DbConnectionOptions userOptions\', \'Comment 208: DbConnectionInternal oldConnection\', \'Comment 209: DbConnectionInternal& connection) at Microsoft.Data.ProviderBase.DbConnectionInternal.TryOpenConnectionInternal(DbConnection outerConnection\', \'Comment 210: DbConnectionFactory connectionFactory\', \'Comment 211: TaskCompletionSource`1 retry\', \'Comment 212: DbConnectionOptions userOptions) at Microsoft.Data.SqlClient.SqlConnection.TryOpen(TaskCompletionSource`1 retry\', \'Comment 213: SqlConnectionOverrides overrides) at Microsoft.Data.SqlClient.SqlConnection.Open(SqlConnectionOverrides overrides) at Microsoft.EntityFrameworkCore.Storage.RelationalConnection.OpenInternal(Boolean errorsExpected) at Microsoft.EntityFrameworkCore.Storage.RelationalConnection.Open(Boolean errorsExpected) at Microsoft.EntityFrameworkCore.Storage.RelationalCommand.ExecuteReader(RelationalCommandParameterObject parameterObject) at Microsoft.EntityFrameworkCore.Query.Internal.FromSqlQueryingEnumerable`1.Enumerator.InitializeReader(Enumerator enumerator) at Microsoft.EntityFrameworkCore.SqlServer.Storage.Internal.SqlServerExecutionStrategy.Execute[TState,TResult](TState state\', \'Comment 214: Func`3 operation\', \'Comment 215: Func`3 verifySucceeded) at Microsoft.EntityFrameworkCore.Query.Internal.FromSqlQueryingEnumerable`1.Enumerator.MoveNext()ClientConnectionId:00000000-0000-0000-0000-000000000000Error Number:53,State:0,Class:20"Microsoft.Data.SqlClient.SqlException (0x80131904): A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider\', \'Comment 216: error: 40 - Could not open a connection to SQL Server) ---> System.ComponentModel.Win32Exception (53): The network path was not found. at Microsoft.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj\', \'Comment 217: Boolean callerHasConnectionLock\', \'Comment 218: Boolean asyncClose) at Microsoft.Data.SqlClient.TdsParser.Connect(ServerInfo serverInfo\', \'Comment 219: SqlInternalConnectionTds connHandler\', \'Comment 220: Boolean ignoreSniOpenTimeout\', \'Comment 221: Int64 timerExpire\', \'Comment 222: Boolean encrypt\', \'Comment 223: Boolean trustServerCert\', \'Comment 224: Boolean integratedSecurity\', \'Comment 225: Boolean withFailover\', \'Comment 226: SqlAuthenticationMethod authType) at Microsoft.Data.SqlClient.SqlInternalConnectionTds.AttemptOneLogin(ServerInfo serverInfo\', \'Comment 227: String newPassword\', \'Comment 228: SecureString newSecurePassword\', \'Comment 229: Boolean ignoreSniOpenTimeout\', \'Comment 230: TimeoutTimer timeout\', \'Comment 231: Boolean withFailover) at Microsoft.Data.SqlClient.SqlInternalConnectionTds.LoginNoFailover(ServerInfo serverInfo\', \'Comment 232: String newPassword\', \'Comment 233: SecureString newSecurePassword\', \'Comment 234: Boolean redirectedUserInstance\', \'Comment 235: SqlConnectionString connectionOptions\', \'Comment 236: SqlCredential credential\', \'Comment 237: TimeoutTimer timeout) at Microsoft.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(TimeoutTimer timeout\', \'Comment 238: SqlConnectionString connectionOptions\', \'Comment 239: SqlCredential credential\', \'Comment 240: String newPassword\', \'Comment 241: SecureString newSecurePassword\', \'Comment 242: Boolean redirectedUserInstance) at Microsoft.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity\', \'Comment 243: SqlConnectionString connectionOptions\', \'Comment 244: SqlCredential credential\', \'Comment 245: Object providerInfo\', \'Comment 246: String newPassword\', \'Comment 247: SecureString newSecurePassword\', \'Comment 248: Boolean redirectedUserInstance\', \'Comment 249: SqlConnectionString userConnectionOptions\', \'Comment 250: SessionData reconnectSessionData\', \'Comment 251: Boolean applyTransientFaultHandling\', \'Comment 252: String accessToken\', \'Comment 253: DbConnectionPool pool) at Microsoft.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options\', \'Comment 254: DbConnectionPoolKey poolKey\', \'Comment 255: Object poolGroupProviderInfo\', \'Comment 256: DbConnectionPool pool\', \'Comment 257: DbConnection owningConnection\', \'Comment 258: DbConnectionOptions userOptions) at Microsoft.Data.ProviderBase.DbConnectionFactory.CreatePooledConnection(DbConnectionPool pool\', \'Comment 259: DbConnection owningObject\', \'Comment 260: DbConnectionOptions options\', \'Comment 261: DbConnectionPoolKey poolKey\', \'Comment 262: DbConnectionOptions userOptions) at Microsoft.Data.ProviderBase.DbConnectionPool.CreateObject(DbConnection owningObject\', \'Comment 263: DbConnectionOptions userOptions\', \'Comment 264: DbConnectionInternal oldConnection) at Microsoft.Data.ProviderBase.DbConnectionPool.UserCreateRequest(DbConnection owningObject\', \'Comment 265: DbConnectionOptions userOptions\', \'Comment 266: DbConnectionInternal oldConnection) at Microsoft.Data.ProviderBase.DbConnectionPool.TryGetConnection(DbConnection owningObject\', \'Comment 267: UInt32 waitForMultipleObjectsTimeout\', \'Comment 268: Boolean allowCreate\', \'Comment 269: Boolean onlyOneCheckConnection\', \'Comment 270: DbConnectionOptions userOptions\', \'Comment 271: DbConnectionInternal& connection) at Microsoft.Data.ProviderBase.DbConnectionPool.TryGetConnection(DbConnection owningObject\', \'Comment 272: TaskCompletionSource`1 retry\', \'Comment 273: DbConnectionOptions userOptions\', \'Comment 274: DbConnectionInternal& connection) at Microsoft.Data.ProviderBase.DbConnectionFactory.TryGetConnection(DbConnection owningConnection\', \'Comment 275: TaskCompletionSource`1 retry\', \'Comment 276: DbConnectionOptions userOptions\', \'Comment 277: DbConnectionInternal oldConnection\', \'Comment 278: DbConnectionInternal& connection) at Microsoft.Data.ProviderBase.DbConnectionInternal.TryOpenConnectionInternal(DbConnection outerConnection\', \'Comment 279: DbConnectionFactory connectionFactory\', \'Comment 280: TaskCompletionSource`1 retry\', \'Comment 281: DbConnectionOptions userOptions) at Microsoft.Data.SqlClient.SqlConnection.TryOpen(TaskCompletionSource`1 retry\', \'Comment 282: SqlConnectionOverrides overrides) at Microsoft.Data.SqlClient.SqlConnection.Open(SqlConnectionOverrides overrides) at Microsoft.EntityFrameworkCore.Storage.RelationalConnection.OpenInternal(Boolean errorsExpected) at Microsoft.EntityFrameworkCore.Storage.RelationalConnection.Open(Boolean errorsExpected) at Microsoft.EntityFrameworkCore.Storage.RelationalCommand.ExecuteReader(RelationalCommandParameterObject parameterObject) at Microsoft.EntityFrameworkCore.Query.Internal.FromSqlQueryingEnumerable`1.Enumerator.InitializeReader(Enumerator enumerator) at Microsoft.EntityFrameworkCore.SqlServer.Storage.Internal.SqlServerExecutionStrategy.Execute[TState,TResult](TState state\', \'Comment 283: Func`3 operation\', "Comment 284: Func`3 verifySucceeded) at Microsoft.EntityFrameworkCore.Query.Internal.FromSqlQueryingEnumerable`1.Enumerator.MoveNext()ClientConnectionId:00000000-0000-0000-0000-000000000000Error Number:53,State:0,Class:20{code}\'", "Comment 285: \'Ani Windows ani SQl authentication!image-2023-03-05-19-04-14-767.png!\'", "Comment 286: \'Hi ReyOn our side we see PCS issue connection", \'Comment 287: it was not working since 13:45. Can you please check with PCS provider in the mean time? Additionally\', "Comment 288: I cannot connect to exchange.Regards\'", \'Comment 289: "Servers where shutdown while factory wa not running.I\\\'m able to connect to the exchange !image-2!"\', "Comment 290: \'I see the PrO are in the exchange Can you tell me what you did?!image-3!\'", "Comment 291: \'Yes", "Comment 292: now it is available for me as well and I can see Orders:!image-2023-03-05-19-35-38-435.png!\'", "Comment 293: \'Errors in logs indicated issue with connection. I just restarted application pools.Regards\'", "Comment 294: \'Rey", "Comment 295: please confirm if we can close this task :)\'", "Comment 296: \'Line 2 ruszył!image-2023-03-05-19-41-58-743.png!\'", \'Comment 297: "I\\\'m waiting for the factory to confirm."\', "Comment 298: \'Sure. Waiting for their feedback then\'", "Comment 299: \'All good. Thank you for the help. Ticket can be closed\'", "Comment 300: \'Thank you\']"]\nRelated Issues:\n[]\n\n### End'}
349	{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8683\n\n### Instruction:\nThe system is not locking automatically lot number expired, I checked the configuration and is enable.\r\n\r\n Could you check why is not working?\r\n\r\nThank you\r\n\r\n\n\n### Response:\n["Comment 1: [\'!image!!image-1!\'", "Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", "Comment 3: \'https://helpdesk.kotrak.com/browse/DAP-13384\'", "Comment 4: \'HelloI can see that similar issue is alreadyprocessed according tohttps://helpdesk.kotrak.com/browse/DGS-8668Please be informed that we have forwarded the issue to the development team in order to internal analysis.May we close this task and work in this first task only ?\'", \'Comment 5: "Sorry Agnieszka\', "Comment 6: I didn\'t see the task opened by Maicon. Yes", \'Comment 7: you can close this one. Thank you"]\']\nRelated Issues:\n[\'DGS-8668\', \'DAP-13382\', \'DAP-13384\']\n\n### End'}
350	{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8682\n\n### Instruction:\nwe have problem in report MaterialRequirementPlaningForRawMaterials, system is not considering orders IO Out to calculate the report.\r\n\r\nexample IO IO-637782830/23/TRN\r\nitem 21560 - 2000kg - delivery date 16/March/2023\r\nit\'s not available in report\r\n\r\n\r\nCould you check why we have this error and fix it? It\'s urgent have correct information in this report, because we schedule purchase orders and transfers using this report.\r\n\r\n\r\nThank you\r\n\r\n\n\n### Response:\n["Comment 1: [\'!image!!image-1!!image-2![^List - 2023-03-03T134053.344.xlsx] _(17 kB)_\'", "Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", "Comment 3: \'Hello on your screen there was no warehouse src code", \'Comment 4: by now it is :Could you check it again also\', "Comment 5: what exact dates You use during report generation ?!image-2023-03-03-18-35-56-614.png!\'", \'Comment 6: "Hello,I was using view per element and in this screen is not whowing warehouse src code\', "Comment 7: I don\'t know why", "Comment 8: do you know?about period I\'m using is 01/Feb/23 till 30/ March/23", \'Comment 9: for check orders and generate report."\', "Comment 10: \'!image-3!\'", "Comment 11: \'Hello guysI think I found the error:The report lists only the RM that are in RawMaterials internal table on the procedure.So", \'Comment 12: if there are any RM tht is not present in RawMaterials\', \'Comment 13: the query will not list it because of the JOINs.You can to check it using MaterialRequirementPlaningForRawMaterials_2 from _2023-03-01_ to _2023-03-31_ and looking for item 21560.We have some SO and IO for it\', "Comment 14: but it is not being listed in the query result.Maybe this can help you.Thank you very much\'", "Comment 15: \'!image-2023-03-06-08-38-06-852.png!\'", \'Comment 16: "hej prośba o weryfikacja z tego co widze procedury lączenie ejst po tabelach z recepturami a podany io jak patrze nie ma recipe id na vt - ale może się mylę \', \'Comment 17: prosze o weryfikacje proceduryselect * from OrderElements where id=\\\'29E4A054-6ACD-4249-B6DA-57B6C8911E2B\\\' select * from OrderElements where id=\\\'29E4A054-6ACD-4249-B6DA-57B6C8911E2B\\\' select * from VehicleTicketBulkDispatchElements where OrderId=\\\'29E4A054-6ACD-4249-B6DA-57B6C8911E2B\\\'!image-2023-03-06-08-54-39-276.png!"\', \'Comment 18: "Tak has been forwarded to the developers\\\' department"\', "Comment 19: \'Raport ten w RC podobno jest już poprawiona. Procedura będzie miała dopisane BR w nazwie. Do sprawdzenia + wgrać poprawne procedury na innych fabrykach + dodać do Bitbucket.\'", "Comment 20: \'[[email protected]]analizowałem ten temat z [[email protected]]. Pan Maicon edytował istniejący SQL. Dokonał zmian których wcześniej nie było. Jeśli klientowi zwraca to odpowiednie wyniki to tak możemy zostawić. Na pozostałych fabrykach mają wersję 8.3 (więc pewnie zmieniony SQL też tam zadziała)", \'Comment 21: natomiast w Caruaru jest 5.3 (tutaj mała szansa\', \'Comment 22: że będzie działać)._I teraz tak\', \'Comment 23: możesz ewentualnie napisać\', \'Comment 24: że zmienione procedury z RC możesz wgrać na inne fabryki oraz założymy task w projekcie DAP\', "Comment 25: aby zaktualizować procedury w projekcie._\'", "Comment 26: \'From our analysis it appears that the request was modified by you", "Comment 27: if such a form works correctly in Rio Claro it can be uploaded in other factories. Can the ticket be closed?\'", "Comment 28: \'Can the ticket be closed?\'", "Comment 29: \'[[email protected]] nie robiłaś rozumiem aktualizacji na innych fabrykach? Więc jeśli nie zmieniałaś", "Comment 30: trzeba też klienta poinformować że nic nie wykonaliśmy.Dodatkowo w ramach tego DGS przed jego zamknięciem trzeba założyć DAP - tutaj możesz się zgłosić do [[email protected]] - i potrzebujemy dodać do Bitbucket te ich zmiany.\'", \'Comment 31: "Hi AgnieszkaWe modified only the report DHBR_... your we didn\\\'t.Can you please fix yours?Thank you"\', "Comment 32: \'[[email protected]]czy możesz założyć DAP do tego taska.\'", "Comment 33: \'We will create separate dap task for that.\'", "Comment 34: \'Procedury z DHBR", \'Comment 35: to procedury pobrane od klienta\', \'Comment 36: natomiast procedury bez tego przedrostku zostały zmodyfikowane na podstawie otrzymanych procedur. Procedury zostały zaktualizowane na środowiskach: TO[Prod]\', "Comment 37: IT[Prod],AP[Prod] i RC[Prod].GU[Prod] nie został zaktualizowany z uwagi na brak uprawnień do logowania na ten serwer[^DHBR_MaterialRequirementPlaningForRawMaterials.sql] [^DHBR_MaterialRequirementPlaningForRawMaterials_2.sql] [^DHBR_MaterialRequirementPlaningForReadyProducts.sql] [^DHBR_MaterialRequirementPlaningForReadyProducts_2.sql] [^MaterialRequirementPlaningForRawMaterials.sql] [^MaterialRequirementPlaningForRawMaterials_2.sql] [^MaterialRequirementPlaningForReadyProducts.sql] [^MaterialRequirementPlaningForReadyProducts_2.sql]\'", "Comment 38: \'wyglada na to ze na guarapes nie ma ver.2!image-2023-04-03-12-42-58-797.png!\'", "Comment 39: \'Procedures have been updated on the following servers: Toledo", "Comment 40: Iteberai,Guararapes,Rio Claro. The procedures we added are our procedures do not have the DHBR prefix.!image-2023-04-03-13-08-50-486.png!Please verify.\'", "Comment 41: \'[[email protected]]w gurarapes nie było procek w wersji v2. więc zmieniłam to co było i na wszelki w zrobiłam backup", "Comment 42: stworzyć 2 dodtakowe procki czy zostawić tak jak jest?!image-2023-04-03-13-10-48-120.png!\'", "Comment 43: \'[[email protected]] v2 jest pod drugi BU w RC", "Comment 44: dlatego występuje tylko w RC.W tych procedurach należy podać odpowiedni BU id. W GU ustawiłaś odpowiedni?\'", "Comment 45: \'podmieniłam\'", \'Comment 46: "HiWell\', "Comment 47: the update was only to copy and past our DHBR_ procedure to yours.The proof that this doesn\'t work is because you are setting VARCHAR value into DATETIME variable with no cast function", \'Comment 48: which causes inconsistency in the result.OK! No problem.You can close this task.Thank you very much!!image-4!"]\']\nRelated Issues:\n[\'DAP-13502\']\n\n### End'}
351	{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8681\n\n### Instruction:\nRecipe 510016 is accepted in DHC but does not arrive in DHP Utrecht.\r\n\r\nI tried to re-send it with zero succes.\n\n### Response:\n["Comment 1: [\'Hello,\\\\r\\\\rWe are investigating your issue. We will inform you about the solution as soon as possible.\\\\r\\\\rRegards\\\\r\\\\r\'", "Comment 2: \'Recipe was synchronized - please verify.!image-2023-03-03-17-47-08-551.png!\'", "Comment 3: \'brakowało w dhc service dhhitema i itema[[DHC][DHCSERVICE] Brak DHHITemu w DHCService\|onenote:https://kotrak.sharepoint.com/sites/erpasysta/Shared%20Documents/Baza%20wiedzy/Baza%20Wiedzy%20-%20ERPSD/Klienci/DEHEUS/DEHEUS%20APPLICATIONS/Holandia%20Premix%20i%20AS400/Baz%20wiedzy%20z%20AS400.one#%5bDHC%5d%5bDHCSERVICE%5d%20Brak%20DHHITemu%20w%20DHCService&section-id=\\\\\\\\{9BB564BA-0B58-4580-B9E0-F3CF9D6D80A7}&page-id=\\\\\\\\{8F28118E-19AC-49AA-BE70-8033239AB278}&end] ([Widok sieci Web\|https://kotrak.sharepoint.com/sites/erpasysta/_layouts/OneNote.aspx?id=%2Fsites%2Ferpasysta%2FShared%20Documents%2FBaza%20wiedzy%2FBaza%20Wiedzy%20-%20ERPSD&wd=target%28Klienci%2FDEHEUS%2FDEHEUS%20APPLICATIONS%2FHolandia%20Premix%20i%20AS400%2FBaz%20wiedzy%20z%20AS400.one%7C9BB564BA-0B58-4580-B9E0-F3CF9D6D80A7%2F%5BDHC%5D%5BDHCSERVICE%5D%20Brak%20DHHITemu%20w%20DHCService%7C8F28118E-19AC-49AA-BE70-8033239AB278%2F%29])\'", "Comment 4: \'I noticed both versions of the recipe arrived in DHP.You can close the ticket", "Comment 5: thanks for the support.Regards,Rob\']"]\nRelated Issues:\n[]\n\n### End'}
352	{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8680\n\n### Instruction:\nI set \'tarwe\' and \'feed\' to the next round and on the line with \'tarwe\' the value = 0€, why?\r\n customer in MAS NL = 200244 round = 200244/0319/0001\r\n I will send a screenshot to Damian\r\n\r\n\xa0\r\n\r\n!image-2023-03-03-14-57-05-954.png!\n\n### Response:\n["Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", \'Comment 2: "Hello,On this Feed sale are lines without proper values\', \'Comment 3: there are no values in column \\\'Price\\\' and \\\'VAT Rate\\\' and system are not able to calculate moving feed.System calculate \\\'Weight to move\\\' * \\\'Price\\\' and also by \\\'VAT Rate\\\' to calculate VAT Value.!image-2023-03-03-15-12-46-541.png!Regards"\', "Comment 4: \'Is this solved?\'", \'Comment 5: "It was caused by manually added line without values\', \'Comment 6: we didn\\\'t change anything in the system.[[email protected]]please inform us that everything is right and we can close this task."\', "Comment 7: \'[[email protected]]could we close the task?\'", "Comment 8: \'Yes can be closed\']"]\nRelated Issues:\n[]\n\n### End'}
353	{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8679\n\n### Instruction:\nWhen a credit is created it should just create a negative copy. Now it seems when the credit PI is created in Intense the system checks again the BP Tax Group (which has been changed in the mean time), but that should not be the case.\r\n\r\n\xa0\r\n\r\nCPI-M/2023/0148 !image-2023-03-03-11-29-14-074.png!\r\n\r\nPI-RLM/2023/0403\r\n\r\n!image-2023-03-03-11-28-57-185.png!\n\n### Response:\n[\'Comment 1: ["Wygląda na to\', \'Comment 2: że dokumenty są skorygowane przez akcję \\\'Create reverse SR\\\' i akcja \\\'Create PI from PI (Reverse SR)\\\' działa inaczej niż zwykła akcja do tworzenia korekty PI \\\'Create correction Invoice from PI (MAS NL)\\\' i niepotrzebnie przeliczane są niektóre wartości zamiast być skorygowane względem pierwotnego dokumentu.Do sprawdzaenia akcje korygowania dokumentów dla Reverse SR w MAS NL i MAS BE (zarówno korekty PI jak i SI)!image-2023-03-03-11-32-30-447.png! * Create PI from PI (Reverse SR)!image-2023-03-03-11-35-20-525.png! * Create correction Invoice from PI (MAS NL)!image-2023-03-03-11-34-41-372.png!"\', "Comment 3: \'Do przygotowania zestawienie faktur korekt", "Comment 4: które mogą się różnić od oryginalnych faktury korygowanych i np. BP TAX Group jest inne na obu dokumentach.!image-2023-03-03-13-58-50-015.png!\'", \'Comment 5: "Functionality of reversing SR has been modified (like for invoices created not from SR\\\'s).Now when PI and SI is credited\', \'Comment 6: values of BP TAX Group and other values which should be always the same like on original invoice are copied for Credit invoice.This is implemented on test and production environment as well\', \'Comment 7: for MAS NL and MAS BE sector.You can verify it.We will prepare also report about credit and credited invoices where elements are different\', \'Comment 8: and we\\\'ll attach report to this task.Regards"\', "Comment 9: \'Yes", "Comment 10: please show me the report.\'", "Comment 11: \'Here is a report with source invoices and credit invoices with different VAT Rate and BP TAX Group on elements.[^DGS-8679_credited_invoices_report.xlsx]Total there are 16 cases when this values are different.Please let us know that should we change VAT Rate and BP TAX Group for credit invoices.Regards\'", \'Comment 12: "zapytanie pod raport z ExcelaSELECT s.Doc_FullNumber AS \\\'Number source\\\',s.Doc_ID AS \\\'ID source\\\',c.Doc_FullNumber AS \\\'Number credit\\\',c.Doc_ID AS \\\'ID credit\\\',se.Del_SeqNo AS \\\'Elm No source\\\',ce.Del_SeqNo AS \\\'Elm No credit\\\',(SELECT Itm_Code FROM Items WHERE Itm_ID = se.Del_ItmID) AS \\\'Item source\\\',(SELECT Itm_Code FROM Items WHERE Itm_ID = ce.Del_ItmID) AS \\\'Item credit\\\',se.Del_VATRate AS \\\'VAT Rate source\\\',ce.Del_VATRate AS \\\'VAT Rate credit\\\',CASE WHEN se.Del_VATRate != ce.Del_VATRate THEN 1 END AS \\\'VAT Rate difference\\\',(SELECT DIC_Svalue FROM Dictionaries WHERE DIC_ID = se.Del_IntColumn14) AS \\\'BP TAX Group source\\\',(SELECT DIC_Svalue FROM Dictionaries WHERE DIC_ID =ce.Del_IntColumn14) AS \\\'BP TAX Group credit\\\',CASE WHEN se.Del_IntColumn14 != ce.Del_IntColumn14 THEN 1 END AS \\\'BP TAX GROUP difference\\\'FROM Documents AS s JOIN Documents AS c ON c.Doc_LeadingDocID = s.Doc_IDJOIN DocElems AS se ON s.Doc_ID = se.Del_DocIDJOIN DocElems AS ce ON c.Doc_ID = ce.Del_DocIDWHEREs.Doc_DdfID IN (13\', \'Comment 13: 14\', \'Comment 14: 42\', \'Comment 15: 43)AND c.Doc_DdfID IN (13\', \'Comment 16: 14\', \'Comment 17: 42\', \'Comment 18: 43)AND s.Doc_DdfID = c.Doc_DdfIDAND c.Doc_IntColumn2 = 1AND ABS(ce.Del_ItmID) = ABS(se.Del_ItmID)AND ABS(ISNULL(ce.Del_Weight,0)) = ABS(ISNULL(se.Del_Weight,0))AND ABS(ISNULL(ce.Del_Price\', \'Comment 19: 0)) = ABS(ISNULL(se.Del_Price,0))AND (se.Del_VATRate != ce.Del_VATRateOR se.Del_IntColumn14 != ce.Del_IntColumn14ORse.Del_IntColumn6 != ce.Del_IntColumn6ORse.Del_ShortStringColumn5 != ce.Del_ShortStringColumn5)ORDER BY [Number source]"\', "Comment 20: \'Can be closed.\']"]\nRelated Issues:\n[]\n\n### End'}
354	{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8678\n\n### Instruction:\nHi\r\n\r\nDHP is out.\r\nWe found ajanuszewska logged in this server.\r\nNow everything is off.\r\n\r\nFactory is stopped\r\n\r\nPlease help\r\n\r\nThanks\n\n### Response:\n["Comment 1: [\'!image!!image-1!\'", "Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", "Comment 3: \'!image-2!\'", "Comment 4: \'Please check it all work ok now,\'", "Comment 5: \'Hi AgnieszkaWe are testing reports", "Comment 6: but seems somethig is not working yet:!image-3!\'", "Comment 7: \'Now is working. Do you know why we have the error?\'", "Comment 8: \'Hi AgnieszkaSSRS are online too.We are now waiting for instructions about folder permissions.Thank you\'", "Comment 9: \'there were problems with permissions on folder Kotrak", \'Comment 10: and DHP_IIS\', "Comment 11: it also caused before that problem with generating xml files it seems to be the firstthere was not group users in this properties : !image-2023-03-02-18-56-00-746.png!\'", "Comment 12: \'May we close the task ?\'", \'Comment 13: "HiThat\\\'s weird. No folder permission were changed from our side.Well\', "Comment 14: so there\'s nothing for me to do know about it", \'Comment 15: right?In that case\', \'Comment 16: Yes! You can close this taskThank you very much"\', \'Comment 17: "[[email protected]] Probably IT shared main folder dhp3.0 instead of XML folder. During this option - Sharing - did IT delete permission for group \\\'Users\\\' ?!image-2023-03-03-12-36-51-930!!image-2023-03-03-12-42-04-919!"\', "Comment 18: \'[[DHP 3.0] brak logów tekstowych dla modułów. Nieaktualne logi.\|onenote:https://kotrak.sharepoint.com/sites/erpasysta/Shared%20Documents/Baza%20wiedzy/Baza%20Wiedzy%20-%20ERPSD/Klienci/DEHEUS/DEHEUS%20APPLICATIONS/Brazil/Baza%20wiedzy.one#%5bDHP%203.0%5d%20brak%20log%C3%B3w%20tekstowych%20dla%20modu%C5%82%C3%B3w.%20Nieaktualne&section-id=\\\\\\\\{05DF1439-683C-45FE-8260-61E2EC66DC91}&page-id=\\\\\\\\{91116E2F-1387-4F03-B87C-A3F9B99FF906}&end] ([Widok sieci Web\|https://kotrak.sharepoint.com/sites/erpasysta/_layouts/OneNote.aspx?id=%2Fsites%2Ferpasysta%2FShared%20Documents%2FBaza%20wiedzy%2FBaza%20Wiedzy%20-%20ERPSD&wd=target%28Klienci%2FDEHEUS%2FDEHEUS%20APPLICATIONS%2FBrazil%2FBaza%20wiedzy.one%7C05DF1439-683C-45FE-8260-61E2EC66DC91%2F%5BDHP%203.0%5D%20brak%20log%C3%B3w%20tekstowych%20dla%20modu%C5%82%C3%B3w.%20Nieaktualne%7C91116E2F-1387-4F03-B87C-A3F9B99FF906%2F%29])\']"]\nRelated Issues:\n[\'DGS-8706\']\n\n### End'}
355	{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8677\n\n### Instruction:\nwe have problem to generate XML, system is showing error message when we click in Generate XML after add all information.\r\nAO-0002/03/23-90\r\n\r\nIt\'s urgent fix to send for customer the result.\r\n\n\n### Response:\n["Comment 1: [\'!image!!MicrosoftTeams-image (55)!\'", "Comment 2: \'D:\\\\\\\\Kotrak\\\\\\\\dhp30_IIS\\\\\\\\XML\'", \'Comment 3: \\\'2023-03-02 10:55:02 (ec169787-bcfe-4de8-b08f-bb25637081cd/Plant.QAM.BusinessLogic/BR-1-SV-VM0702/23916/74) [Error] Kotrak.Common.Infrastructure.Middleware.LoggingMiddleware.ControllerLoggingMiddleware - Error during request{ "scheme": "http"\', \'Comment 4: "host": { "Value": "br-1-sv-vm0702:84"\', \'Comment 5: "HasValue": true\', \'Comment 6: "Host": "br-1-sv-vm0702"\', \'Comment 7: "Port": 84 }\', \'Comment 8: "path": "/api/analyses/order/exportXml"\', \'Comment 9: "queryString": []\', \'Comment 10: "requestBody": "\\\\\\\\{\\\\\\\\"directoryPath\\\\\\\\":\\\\\\\\"D:\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\Kotrak\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\dhp30_IIS\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\XML\\\\\\\\",\\\\\\\\"package\\\\\\\\":\\\\\\\\"PROFI\\\\\\\\",\\\\\\\\"advice\\\\\\\\":\\\\\\\\"Normal\\\\\\\\",\\\\\\\\"toInvoice\\\\\\\\":false,\\\\\\\\"grassCut\\\\\\\\":\\\\\\\\"1\\\\\\\\",\\\\\\\\"description\\\\\\\\":\\\\\\\\"Silagem de Milho\\\\\\\\",\\\\\\\\"farmerCompany\\\\\\\\":\\\\\\\\"Marcelo Jose do Prado\\\\\\\\",\\\\\\\\"farmerPoBox\\\\\\\\":\\\\\\\\"-\\\\\\\\",\\\\\\\\"farmerCity\\\\\\\\":\\\\\\\\"Santa Rita D´Oeste\\\\\\\\",\\\\\\\\"farmerTin\\\\\\\\":\\\\\\\\"-\\\\\\\\",\\\\\\\\"farmerStreet\\\\\\\\":\\\\\\\\"Sitio NS Auxiliadora\\\\\\\\",\\\\\\\\"lotPitField\\\\\\\\":\\\\\\\\"Silo Compra\\\\\\\\",\\\\\\\\"typeCultivar\\\\\\\\":\\\\\\\\"Milho\\\\\\\\",\\\\\\\\"cutDate\\\\\\\\":\\\\\\\\"2023-02-01T03:00:00.000Z\\\\\\\\",\\\\\\\\"harvestDate\\\\\\\\":\\\\\\\\"2023-02-01T03:00:00.000Z\\\\\\\\",\\\\\\\\"loggedUser\\\\\\\\":{\\\\\\\\"id\\\\\\\\":\\\\\\\\"250f7b61-a6ab-4922-af4d-8ef98f9ad569\\\\\\\\",\\\\\\\\"userName\\\\\\\\":\\\\\\\\"tbanin\\\\\\\\"},\\\\\\\\"employee\\\\\\\\":\\\\\\\\{\\\\\\\\"id\\\\\\\\":\\\\\\\\"43a1b7f5-fa38-416d-bca4-6c2cb2da404b\\\\\\\\",\\\\\\\\"name\\\\\\\\":\\\\\\\\"Sergio Meirelles\\\\\\\\",\\\\\\\\"email\\\\\\\\":\\\\\\\\"[email protected]\\\\\\\\"},\\\\\\\\"samplingDate\\\\\\\\":\\\\\\\\"2023-02-22T03:00:00.000Z\\\\\\\\",\\\\\\\\"analysisOrders\\\\\\\\":[\\\\\\\\{\\\\\\\\"id\\\\\\\\":\\\\\\\\"74fa0fa7-dc7b-4f64-991c-6ded543e2980\\\\\\\\",\\\\\\\\"articleId\\\\\\\\":\\\\\\\\"7418a724-cbd2-4fa9-9bd5-b8649ebdad49\\\\\\\\",\\\\\\\\"articleCode\\\\\\\\":\\\\\\\\"LX178\\\\\\\\",\\\\\\\\"articleName\\\\\\\\":\\\\\\\\"SILAGEM DE MILHO\\\\\\\\",\\\\\\\\"sampleCode\\\\\\\\":\\\\\\\\"90230302001\\\\\\\\",\\\\\\\\"sampleItemCode\\\\\\\\":\\\\\\\\"LX178\\\\\\\\",\\\\\\\\"nutrients\\\\\\\\":[{\\\\\\\\"nutrientCode\\\\\\\\":\\\\\\\\"VCRDRYT\\\\\\\\",\\\\\\\\"nutrientName\\\\\\\\":\\\\\\\\"Dm Weight Terra\\\\\\\\",\\\\\\\\"value\\\\\\\\":32.13},\\\\\\\\{\\\\\\\\"nutrientCode\\\\\\\\":\\\\\\\\"VCRDRYI\\\\\\\\",\\\\\\\\"nutrientName\\\\\\\\":\\\\\\\\"Dm Weight In\\\\\\\\",\\\\\\\\"value\\\\\\\\":270.58},\\\\\\\\{\\\\\\\\"nutrientCode\\\\\\\\":\\\\\\\\"VCRDRYO\\\\\\\\",\\\\\\\\"nutrientName\\\\\\\\":\\\\\\\\"Dm Weight Out\\\\\\\\",\\\\\\\\"value\\\\\\\\":95.38}]}]}"}.System.UnauthorizedAccessException: Access to the path \\\\\\\'D:\\\\\\\\Kotrak\\\\\\\\dhp30_IIS\\\\\\\\XML\\\\\\\\DHHIMP90010025.xml\\\\\\\' is denied.\\\'\', "Comment 11: \'[^DHHIMP90010025.xml]\'", "Comment 12: \'[^DHHIMP90010025.xml]^Hello I can see that there is some problem with access to folder.^^I temporarly changed the path in configuration and create new folder.^^Please verify if document is correct^^and let me know if we may change priority to p2 ( tommorow someone from our developers will look at configuration).^^!image-2023-03-02-16-59-46-096.png!^\'", "Comment 13: \'I need to check", "Comment 14: but you can change for P2. Thank you.\'", "Comment 15: \'the fisrt problem with authentication occured at 10:55!image-2023-03-02-19-18-20-465.png!\'", "Comment 16: \'Please try to generate the xml again and check if the problem still occurs.\'", "Comment 17: \'Hi", "Comment 18: the error still occurs. Could you check it?\'", "Comment 19: \'[[email protected]] ścieżka aktualnie jest taka jak poprzednio do XML folder. Folder xmltest został dzisiaj usunięty.\'", "Comment 20: \'Hello in today log I did not see the same error as yesterday ", \'Comment 21: could you provide more detailswhen you get an error? and for what AO?Maybe you may provide information what AO is printed and how to filI in the form\', "Comment 22: that we may use this AO for test it?\'", \'Comment 23: "AgnieszkaI tested now with Tassia and it\\\'s working.Thank you"]\']\nRelated Issues:\n[]\n\n### End'}
356	{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8676\n\n### Instruction:\nHi\r\nPrzy kopiowaniu ZZ na nowy ZZ, który na pozycji ma ilość=0, nie ma możliwości zmiany ilości i kosztu transportu.\r\nJest błąd: Odwołanie do obiektu nie zostało ustawione na wystąpienie obiektu.\r\n\r\n\r\nRafał Boniecki\r\n\n\n### Response:\n["Comment 1: [\'!image!\'", "Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", "Comment 3: \'Looks like a problem with the document and not the functionality", "Comment 4: is it a copy from order 123/3/23?The items of this order start with number 2 !screenshot-1! Did these orders also look like this at the beginning of the ticket?\'", \'Comment 5: "No\', \'Comment 6: it\\\'s copy from ZZ-92"\', \'Comment 7: "z profilera{code:java}declare @ContractId int=10033678--declare @ElementId int=1SELECT SUM(Quantity) QuantityFROMKotrak.calloffsWHEREContractId = @ContractId --AND ContractElementId = @ElementId AND--Status <> 6--\\\',N\\\'@ContractId int,@ElementId int\\\',@ContractId=10033678,@ElementId=2{code}{code:java}UPDATE N SET ZaN_Aktywny = 0FROM CDN.ZamNag NJOIN CDN.Sesje S ON (Zan_Aktywny <> 0) AND ZaN_Aktywny = S.SES_SesjaIDWHERE ZaN_GidNumer=@contractId AND (@force = 1 OR S.SES_Aktywna = 1 OR S.SES_Aktywna = 2)\\\',N\\\'@contractId int,@force int\\\',@contractId=9887385,@force=0{code}Problem dotyczy tylko tego zamówienia zz-92/02/2023 - edytując dowolny element. !screenshot-2! "\', "Comment 8: \'zgodnie z rozmową.\'", "Comment 9: \'Hello", "Comment 10: the problem is with this particular order and you just need to edit any element and there is this problem.Attempts to duplicate it on the test fail - please create a new contract not from a copy. In the test it is possible to create a new copy contract for elements with zero quantities.\'", \'Comment 11: "Hi\', "Comment 12: we\'ve done like this when the problem occur", \'Comment 13: but is there any chance to fix this error?"\', \'Comment 14: "Hi\', \'Comment 15: are there more cases?Can\\\'t this contract be closed?Do we have a path to the error?It would make it easier to analyze."\', \'Comment 16: "For now it was 1 case with this error. We made a new ZZ manually. I think this task is to close. We\\\'ll analyze once more\', \'Comment 17: when problem return."]\']\nRelated Issues:\n[]\n\n### End'}
357	{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8675\n\n### Instruction:\nThere are cases that we need to add an SR to Intense just for registration purposes. So just because we need to have correct technical results. We don\'t do anything financially with these slaughter reports.\r\n\r\nWe need to be able to register a SR registration:\r\n•\tOnly possibility to create registration PI from it \r\n•\tWe won’t use the pricing formula. We will manually give a price (on the invoice, registration purchase)\r\n•\tIt must be calculated within the technical results (we can also just create the registration PI, if this is enough to get these numbers in the technical calculations)\r\n\r\nCould you help us with this? \r\n\n\n### Response:\n["Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", \'Comment 2: "Now it\\\'s possible to manualy add Slaughtery Report in MAS NL and MAS BE.Is it sufficient or should we think to add some validations - to allow create only Purchase Invoices from SR?The process normally looks little differently in MAS NL and MAS BE\', \'Comment 3: so in both sectors it should be possible to create only PI from SR? * In MAS NL from SR is created SI * In MAS BE from SR is created PII think if SR will be connected with round and invoice will be also properly linked with SR values should be included in technical results\', "Comment 4: but we should analyze it deeper.Is it needed to get values from this SR and PI to technical results but we don\'t want to include this invoice in all documents - Round", \'Comment 5: Financial Statement\', \'Comment 6: Saldo to pay\', \'Comment 7: right?"\', \'Comment 8: "Yes\', \'Comment 9: it should be an SR with a registration type somewhere.In case of registration indeed it should be only possible to create a registration PI. This registration can be included on the round and financial statement\', \'Comment 10: however it should indeed not be on the S2P (the same as all other registration PI\\\'s)."\', "Comment 11: \'WHen do you think this is ready?\'", "Comment 12: \'Please note that in MAS NL we normally start the process with a SI", "Comment 13: but in case of a registration SR we only create a registration purchase invoice.\'", \'Comment 14: "{quote}Yes\', \'Comment 15: it should be an SR with a registration type somewhere.In case of registration indeed it should be only possible to create a registration PI.This registration can be included on the round and financial statement\', "Comment 16: however it should indeed not be on the S2P (the same as all other registration PI\'s).{quote}Does it mean that we should add new field on Slaughtery Report - some checbox with label \'Registered\' or other distincion?We can add action to generate Purchase Invoice with Registered type from this kind of Slaughtery reports and other buttons to create invoices then will be hidden. Will it be sufficient?We need to verify all calculations in technical results procedure to handle it in right way", \'Comment 17: because some calculation base on invoices which are linked in normal way (for MAS NL - SR -> SI -> PI\', \'Comment 18: for MAS BE - SR -> PI -> SI) or add to all calculations new type of slaughtery report (with checbox or orher distintinction)."\', \'Comment 19: "Does it mean that we should add new field on Slaughtery Report - some checbox with label \\\'Registered\\\' or other distincion? --> YESWe can add action to generate Purchase Invoice with Registered type from this kind of Slaughtery reports and other buttons to create invoices then will be hidden. Will it be sufficient? --> YES"\', "Comment 20: \'Slaughtery Report", \'Comment 21: który będzie korektą oryginalnego powinien być tworzony w całości ręcznie przez użytkownika z Inboxa.Purchase Invoice\', \'Comment 22: który będzie generowany ze Slaughtery reportu powinien być liczony podobnie jak faktury PI/SI (w zależności od sektora). Przy tych generacjach są nasze procedury\', \'Comment 23: które wyliczają wartości na PI/SI - np. KR_CalculationSlaughteryReportToPurchaseInvoice i powinno być to wyliczane analogicznie\', "Comment 24: jedynie bez danych z kontraktu i pricing formula. Ceny na fakturach PI powinny być wprowadzane ręcznie.\'", "Comment 25: \'For technical results values from PI should be most important.\'", \'Comment 26: "[[email protected]]We divided this task to 2 steps: # Functionality to creating SR with checkbox \\\'Registered\\\' and \\\'Create Purchase Invoice\\\' Button \\\'Create Purchase Invoice\\\' is visible when checkbox\\\'Registered\\\' on SR is marked. Other buttons for \\\'Create Sales Invoice\\\' shouldn\\\'t be visible then. # Handle calculating technical results from this kind of slaughtery reports and purchase invoicesFor now from step 1 functionality has been created on IBIP_DH_TEST and it\\\'s possible to test it. Now it\\\'s done in MAS NL sector only and you can verify it there and then we can implement it also in MAS BE.You can verify that it works properly\', \'Comment 27: especially if the Purchase Invoices gets all and proper elements and values from SR (we have used procedure for creating purchase invoice from normal process with SR).!image-2023-03-28-10-25-10-052.png!!image-2023-03-28-10-29-22-773.png!"\', \'Comment 28: "Hello Damian,I checked it\', \'Comment 29: but I don\\\'t see the checkbox yet in DH TEST. Did I do something wrong?!image!"\', \'Comment 30: "Hello Steffen,It\\\'s implemented in MAS NL sector so far."\', \'Comment 31: \\\'We need to be able to somewhere include the price. Normally we use the pricing formula for this but for registration SR\\\\\\\'s we won\\\\\\\'t use it. When the checkbox "Registered" is marked we should see an additional field to put in the price.\\\'\', \'Comment 32: "In my eyes\', \'Comment 33: the pricing formula may be used as well. Mostly it\\\'s that price that we are going to use anyways. Maybe I missed the clue earlier that this isn\\\'t an option?"\', \'Comment 34: \\\'{quote}We need to be able to somewhere include the price. Normally we use the pricing formula for this but for registration SR\\\\\\\'s we won\\\\\\\'t use it.When the checkbox "Registered" is marked we should see an additional field to put in the price.{quote}{quote}In my eyes\', "Comment 35: the pricing formula may be used as well. Mostly it\\\\\'s that price that we are going to use anyways. Maybe I missed the clue earlier that this isn\\\\\'t an option?{quote}How would you like to put the price? it should be one field with price and it should be on SR or maybe it should be possible to put price on invoice?Maybe we can use somehow existing fields from SR or the same fields like in normal process?\'", \'Comment 36: "According to me\', "Comment 37: it may be complete the same process as a regular/financed slaughter report (with the pricing formula). It just has to include these numbers also in the calculations of the technical results. But I\'ll let Mitch answer", \'Comment 38: maybe he still has other insights."\', "Comment 39: \'Afte discussion I agree with Steffen. Please use the pricing formula for this just like in all other cases.\'", "Comment 40: \'All right", \'Comment 41: then itshould works with pricing formula like in normal process\', "Comment 42: you can verify that it works and prices are calculated.When you select round I think it will be possible to calculate values properly.Maybe only on IBIP_DH_TEST Price List is not filled for last months.Could you verify that is sufficient and this part of modification works properly?\'", \'Comment 43: "Prices are calculated (correctly it seems). However I didn\\\'t select \\\'registration\\\' somewhere on the slaughter report because there wasn\\\'t a field. Do I need to select \\\'regular purchase\\\' here and then switch the type in the invoice?!image-2!!image-3!"\', "Comment 44: \'I have tested this as well and it looks good. I see the checkbox: !image-1!\'", "Comment 45: \'Oh yes", \'Comment 46: my bad. Probably only was in MAS NL TEST. But if Mitch says it works\', "Comment 47: I trust that.\'", \'Comment 48: "Ok\', \'Comment 49: it seems that works properly\', "Comment 50: so we\'ll implement also this solution to MAS BE on Test environment.We\'ll inform you when it will be ready to tests.This will be 1 st part of this task", \'Comment 51: 2 nd more complex will be about modifications in technical results calculations.Do you think that we should rather based in calculations on values from this Purchase Invoice or Slaughtery Report?On Purchase Invoice generated from this SR will be lines with items similar like on regular SR?As we discussed recently about changes in technical results calculations there was a statement that we should basedmore on PI than on SR (of course not all values can be collected from PI\', \'Comment 52: I refer to values which are on both documents PI and SR)."\', "Comment 53: \'Do you think that we should rather based in calculations on values from this Purchase Invoice or Slaughtery Report? --> PIOn Purchase Invoice generated from this SR will be lines with items similar like on regular SR? --> YES\'", "Comment 54: \'Now", "Comment 55: we got similar situation in MAS BE like MAS NL. You can test it. We still work on second stepnamely * Handle calculating technical results from this kind of slaughtery reports and purchase invoices\'", "Comment 56: \'I can see the field in MAS BE test now as well", "Comment 57: yes.\'", "Comment 58: \'Could you specified in columns for records on yellow which technical results should be credited by new process and from which document should be selected values to correct original values.\|Should correct technical result?\|SR credit\|PI generated from SR credit\|Remarks\|[^Technical Results.xlsx]\'", "Comment 59: \'{color:black}{color} {color:black}{color} \| \|{color:#000001} Metvriendelijkegroet,{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:white}\\\\u200b{color}{color:#000001}SalutationsCordiales{color} \| \| \| \|{color:#000001} Koen{color} \|{color:#000001} {color} \|{color:#000001} Huibers{color} \| {color:#000001}+31318675600{color} \| \| \|{color:black}{color} {color:black}{color}{color:windowtext}{color}{color:black}{color}!image001!{color:black} <[https://www.de-heus.nl/]>{color} \| \| {color:#006FB7} DEHEUSVOEDERSBELGIEN.V.{color} \| \| \|{color:black} {color} \| \|{color:#000001} LouisPasteurstraat11/201 \\\\u200b3920Lommel{color} \| \| \|{color:#000001} M:{color}{color:#000001}{color}{color:#000001}+32-11-546672{color}{color:#000001} <tel:+32%20-%2011%20-%2054%2066%2072>{color} \| {color:#000001}Ondernemingsnummer:0437.737.739{color} \| _{color:#000001} _Opdite‑mailberichteneventuelebijlage(n)isdedisclaimervantoepassing_ _gepubliceerdopdewebsitevan_ {color}[{color:#000001}{color}{color:#000001} _+ DeHeusVoeders+_{color}{color:#000001} {color}\|https://www.de-heus.nl/privacy-beleid]{color:#000001} _._{color}_ \| \| \| !image002! <[https://www.facebook.com/deheusvoeders]>{color:black}{color} \| \| !image003! <[https://twitter.com/de_heus_voeders]>{color:black}{color} \| \| !image004! <[https://www.youtube.com/channel/UCqkrGebUlFowgumurz-abxQ]>{color:black}{color} \| \| !image005! <[https://www.linkedin.com/company/de-heus-voeders-b-v-/]>{color:black}{color} \| Van: Damian Świstek (Jira) <[email protected]> Verzonden: woensdag 5 april 2023 8:56 Aan: Huibers", "Comment 60: Koen <[email protected]> Onderwerp: DGS-8675 Create SR registration !image006.gif![^doc17951020230404161459.pdf] _(200 kB)_\'", \'Comment 61: "[[email protected]]it\\\'s ready to test in MAS NL sector on test environment with technical results calculations."\', "Comment 62: \'I tested a customer on round 014940/0006/0003 in MAS NL TEST. A few comments: 1. On the registration invoice", \'Comment 63: code SRMT was automatically used for slaughtery revenue in stead of SLAC (screenshot 1)? 2. When I want to archive the SR\', \'Comment 64: the system gives me a warning there are no invoices created\', \'Comment 65: while I did already archive the registration PI (screenshot 2)? For the rest\', \'Comment 66: the the technical results seem good\', \'Comment 67: you can see in the last screenshot. So to me\', "Comment 68: this can be moved to PROD (with attention to the 2 comments).!image-4!!image-5!!image-6!\'", \'Comment 69: "1. I\\\'ve checked procedure which creates PI from SR. Line with Item SRM has been generated on PI because condition for adding line with this item SRM was met Contract SlaughterIn this case on SR value \\\'Deviance\\\' is null\', \'Comment 70: in procedure when SR is linked to CS there is verification that value from CS other conditions 2\', "Comment 71: from column \'Condition\' - here is <50 is less than deviation. Here it\'s not", \'Comment 72: so in this case procedure calculate it like that:KGToPayToFarmer * Amount (47022 * 0,0050)\', \'Comment 73: so there was on invoice value = 235,11.2. Warning during flow performing has been implemented to normal process for Slaughtery Reports to avoid sending to Archive documents - here there are no SI like in normal proces\', "Comment 74: that\'s why is warning. Verification is about SI and PI from SR. We can adjust it if it\'s needed and not display this warning.Should we do any improvements for this process right now", \'Comment 75: do you need to test it on more cases or should we start moving this solution to Prod environment?!image-2023-04-07-13-47-10-761.png!!image-2023-04-07-13-47-26-357.png!"\', "Comment 76: \'1. I hope Steffen can answer", "Comment 77: he knows more about the details of this example.2. This warning can be turned off. We will only create the PI. \'", \'Comment 78: "[[email protected]][[email protected]]It\\\'s ready to test also in MAS BE sector on test environment with technical results calculations.As we discussed recently MAS NL can be move to prod environment\', \'Comment 79: then if in MAS BE also will be good and you confirm that it works properly\', \'Comment 80: we can move to Prod environment solution for both sectors."\', \'Comment 81: "[[email protected]]do przeniesienia na Prod pierwsza część rozwiązania # {quote}Functionality to creating SR with checkbox \\\'Registered\\\' and \\\'Create Purchase Invoice\\\'Button \\\'Create Purchase Invoice\\\' is visible when checkbox\\\'Registered\\\' on SR is marked. Other buttons for \\\'Create Sales Invoice\\\' shouldn\\\'t be visible then.{quote}Jak potwierdzą nam\', \'Comment 82: że dla sektora MAS BE działa poprawnie na test przeliczanie Technical results\', \'Comment 83: to przeniosę 2 część tego taska na Prod."\', "Comment 84: \'I tested it in MAS BE and it worked. For me it can be moved to PROD. Thank you\'", "Comment 85: \'Solution has been moved to Production environment for MAS NL and MAS BE sectors.Please verify and confirm if everything works properly and then we can close task.\'", \'Comment 86: "I will test it now. Just one more question Damian\', "Comment 87: old rounds where we used registrated SR\'s + invoices", \'Comment 88: should they be adapted by now as well\', \'Comment 89: or does it only start now when we tick \\\'registered\\\' on the SR?"\', "Comment 90: \'I actually just tested it myself. I opened a SR of a already finished round", \'Comment 91: ticked "registered" and recalculated the technical results again. Afterwards the numbers modified. So to me\', "Comment 92: it seems to be working.\'", \'Comment 93: "What do you meanregistrated SR\\\'s + invoices which you used? Did you use before this new functionality deployment some solution with SR + invoice to correct some values?Functionality of SR registered (with marked checkbox) will work from now.Technical results are calculated right now with new conditions (including values from this specific type of SR Registered + PI registered created from this registered SR).Nothing should change on old documents\', \'Comment 94: round\', \'Comment 95: calculated values for technical results if there will be no SR Registered (with new checbox)\', \'Comment 96: but if you add some SR registered (with checkbox) for old rounds and when you calculate technical results values will change.!image-2023-04-17-13-25-27-804.png!"\', "Comment 97: \'Yes", \'Comment 98: it is as you say. I had a round where the technical results were wrong because there was a registered PI\', \'Comment 99: but at that time\', \'Comment 100: the box was not yet on the SR. Now that it is\', \'Comment 101: I went back and ticked it\', "Comment 102: and afterwards the values changed on the technical results as I hoped so. So that looks great!\'", "Comment 103: \'Great", "Comment 104: so we can leave this task open until you confirm that everything works properly in more cases or close the task if you decide that it works fine.\']"]\nRelated Issues:\n[\'DGS-8732\', \'DGS-8877\']\n\n### End'}
358	{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8674\n\n### Instruction:\nDH CDN is very slow.\r\nVery low responce.\r\n\r\n\n\n### Response:\n["Comment 1: [\'!image!!image-1!!image-2!!image-3!\'", "Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", "Comment 3: \'!image-2023-03-02-14-20-09-918.png\|width=1092,height=660!\'", "Comment 4: \'!image-2023-03-02-14-21-07-216.png\|width=800,height=528!\'", "Comment 5: \'!image-2023-03-02-14-40-09-605.png!\'", "Comment 6: \'{code:java}ERRORS:\|Cannot generate document \\\\x96 no license. (NowyDokument-81) at Evolution.ErpIntegrator.CdnXL.CdnXL2016.Documents.ExternalOrderTransactions.CdnXL2016ExternalOrderTransactionRepository.CreateHeader(XLExternalOrderTransaction documentHeader) in C:\\\\\\\\TeamCity\\\\\\\\buildAgent\\\\\\\\work\\\\\\\\57a7e278b67a115c\\\\\\\\Evolution.ErpIntegrator\\\\\\\\CdnXL\\\\\\\\Evolution.ErpIntegrator.CdnXL.CdnXL2016\\\\\\\\Documents\\\\\\\\ExternalOrderTransactions\\\\\\\\CdnXL2016ExternalOrderTransactionRepository.cs:line 792023-03-02 10:15:48,966 [9] DEBUG Evolution.ErpIntegrator.DHC.DHC30.Database.DhcTransaction [(null)] - DHC transaction rollback staeted2023-03-02 10:15:48,966 [9] DEBUG Evolution.ErpIntegrator.DHC.DHC30.Database.DhcTransaction [(null)] - DHC transaction rollback finished2023-03-02 10:15:48,969 [9] ERROR Evolution.ErpIntegrator.CdnXL.CdnXL2016.Transactions.XLTransaction [(null)] - XL rollback error - possibly no transactionError of type Evolution.ErpIntegrator.CdnXL.CdnXL2016.XLApiException has been thrown (XLTransakcja - Rollback:-1).API Name - XLTransakcja - RollbackAPI Result - -12023-03-02 10:15:48,969 [9] DEBUG Evolution.ErpIntegrator.CdnXL.CdnXL2016.Transactions.XLTransaction [(null)] - XL transaction rollbacked", \'Comment 7: token ID - 8Q_ZTOCX5a[-Yi6SjF_e_=5---0kDM--2023-03-02 10:15:48,974 [9] DEBUG Evolution.ErpIntegrator.DHC.DHC30.Database.DhcTransaction [(null)] - DHC transaction rollback staeted2023-03-02 10:15:48,974 [9] DEBUG Evolution.ErpIntegrator.DHC.DHC30.Database.DhcTransaction [(null)] - DHC transaction rollback finished2023-03-02 10:15:48,976 [9] ERROR Evolution.ErpIntegrator.CdnXL.CdnXL2016.Transactions.XLTransaction [(null)] - XL rollback error - possibly no transactionError of type Evolution.ErpIntegrator.CdnXL.CdnXL2016.XLApiException has been thrown (XLTransakcja - Rollback:-1).API Name - XLTransakcja - RollbackAPI Result - -12023-03-02 10:15:48,976 [9] DEBUG Evolution.ErpIntegrator.CdnXL.CdnXL2016.Transactions.XLTransaction [(null)] - XL transaction rollbacked\', "Comment 8: token ID - 2023-03-02 10:15:49,035 [9] ERROR Evolution.ErpIntegrator.IntegrationLibrary.Documents.VehicleTickets.GenerateSalesOrderRelease [(null)] - Error of type XLApiException has been thrown (XLNowyDokument:81).API Name - XLNowyDokumentAPI Result - 81ERRORS:\|Cannot generate document \\\\x96 no license. (NowyDokument-81)Error of type Evolution.ErpIntegrator.CdnXL.CdnXL2016.XLApiException has been thrown (XLNowyDokument:81).API Name - XLNowyDokumentAPI Result - 81{code}\'", "Comment 9: \'Restart!image-2023-03-02-14-46-25-930.png!\'", "Comment 10: \'You have done something,Speed is better on this moment\'", "Comment 11: \'Just verified issue. Batch request was quite high", "Comment 12: now it is much lower\'", "Comment 13: \'Now it is normal. Close ticket\']"]\nRelated Issues:\n[]\n\n### End'}
359	{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8673\n\n### Instruction:\nHi, Peter should be able to add relevancy to all item codes.\n\n### Response:\n["Comment 1: [\'!image!\'", "Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", \'Comment 3: "Hi Mitch,Peter Moeliker has rights for edit Relevant sectors on Item Card and he should be able to do it.I think your screen is from \\\'New Item Card\\\' document and there field \\\'Relevant sectors\\\' is disabled for all users. Should we adjust something in the system?Regards"\', "Comment 4: \'Hi", \'Comment 5: yes. PLease make it possible for all users who can create users from the "new item card\\\\\\\' functionality. Here it should indeed be possible to select the relevant sectors as well.With the new functionalitities the multisector table we don\\\\\\\'t need anymore. All items will be send to all sectors\', "Comment 6: right?\'", \'Comment 7: "Hi,Ok\', "Comment 8: this field now is possible to edit for user who have this documents in Inbox or have access to others inbox and can edit other fields on \'New Item Card\' and can process these documents.Please verify that it\'s possible to edit this field - \'Relevant sectors\'{quote}With the new functionalitities the multisector table we don\'t need anymore. All items will be send to all sectors", "Comment 9: right?{quote}Items are created directly as a \'Item card\' in Intense", "Comment 10: but only for Item Group = \'Raw Materials\' and \'Finish products\'", \'Comment 11: so for other items sent from Milas it apperas in Intense as a \\\'New Item Card\\\' and then it\\\'s possible to choose for which sectors it should be created.Then functionality still works I think."\', "Comment 12: \'Can be closed.\']"]\nRelated Issues:\n[]\n\n### End'}
360	{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8672\n\n### Instruction:\nChange Main Target and customer of invoice: ESI.04.02.2023.VEXP to 0674\r\n\n\n### Response:\n["Comment 1: [\'[^cz esi.04.02.2023.vexp.pdf] _(96 kB)_\'", "Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", "Comment 3: \'Customer data has been changed as requested:!image-2023-03-02-13-10-48-587.png!Regards\'", "Comment 4: \'User is checking the change\'", "Comment 5: \'ok\'", "Comment 6: \'Ticket can be closed\']"]\nRelated Issues:\n[]\n\n### End'}
361	{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8671\n\n### Instruction:\nTask from Wiola:\r\n\r\n\n\n### Response:\n["Comment 1: [\'!image!!image-1!\'", "Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", \'Comment 3: "The message informs that remote work for this person has already been introduced on this day. Please provide a screenshot of this employee\\\'s work schedule"\', "Comment 4: \'!image-2!\'", "Comment 5: \'[^Praca_zdalna.docx]\'", "Comment 6: \'Description in the attachment[^Praca_zdalna.docx]\'", "Comment 7: \'Could you please confirm if we can close this task?Regards\'", "Comment 8: \'Hi", "Comment 9: task to close. Thanks.\']"]\nRelated Issues:\n[]\n\n### End'}
362	{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8670\n\n### Instruction:\nHi, from Iwona:\r\n\r\n\n\n### Response:\n["Comment 1: [\'!image!\'", "Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", "Comment 3: \'If this task still actual?I see this payroll in the transfer list!image-2023-03-03-10-31-02-136.png!\'", "Comment 4: \'!image-1!\'", "Comment 5: \'Can I close this task?\'", "Comment 6: \'Yes", "Comment 7: task to close.\']"]\nRelated Issues:\n[]\n\n### End'}
363	{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8669\n\n### Instruction:\nHi, task from Wiola:\r\n\r\n\n\n### Response:\n["Comment 1: [\'!image!\'", "Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", "Comment 3: \'changes on report will take 8 rbg please accept costs.\'", "Comment 4: \'I accept costs.\'", "Comment 5: \'New report has been added in optima. Please verify !screenshot-1! \'", "Comment 6: \'Can we close this issue?\'", "Comment 7: \'Still waiting for response from Wiola.\'", "Comment 8: \'!image-1!\'", \'Comment 9: \\\'When printout parameters are set as below. Employee UM-OSTROWSKA_M is not visible on it. Please let me know about parameters that you set up. !screenshot-2! About additional condition let me know more details.If printout should check only "Zwolnienie chorobowe" absence or another? And second if 31 days must be checked to current date or to date from parameters (below). Then we will sent pricing. !screenshot-3! \\\'\', "Comment 10: \'!image-2!\'", \'Comment 11: \\\'visibility in excel has been corrected. Please verifyAbout additional condition let me know more details.If printout should check only "Zwolnienie chorobowe" absence or another?And second if 31 days must be checked to current date or to date from parameters (below). Then we will sent pricing. !screenshot-3! \\\'\', "Comment 12: \'!image-3!\'", "Comment 13: \'Hi", "Comment 14: can we reopen this task? !image-4!\'", "Comment 15: \'Task has been reopened .We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", "Comment 16: \'Please provide filter and parameters You are generating this raport for.When I run this report for filter!image-2023-04-07-18-18-33-226.png!!image-2023-04-07-18-18-50-963.png!with parametes!image-2023-04-07-18-19-20-064.png!I do not see UM-OSTROWSKA_M on generated raport !image-2023-04-07-18-18-16-389.png!\'", "Comment 17: \'Please", "Comment 18: let me know if expect any additional actions from us regarding this issue? Can we close this ticket?\'", "Comment 19: \'!image-5!\'", "Comment 20: \'In summary", \'Comment 21: the reported modification has been made and the report "Limity nieobecności (dla zaznaczonych)" is working properly.The continuation of the issue concerns "Zestawienie wypłaconych premii" report requiring modification.In this case\', \'Comment 22: please create a new issue\', \'Comment 23: the modification of the report will be valued and after receiving the approval of the costs\', "Comment 24: we will proceed to implement the changes.Could you please confirm if we can close this task?Regards\'", "Comment 25: \'In summary", \'Comment 26: the reported modification has been made and the report "Limity nieobecności (dla zaznaczonych)" is working properly.The continuation of the issue concerns "Zestawienie wypłaconych premii" report requiring modification.In this case\', \'Comment 27: please create a new issue\', \'Comment 28: the modification of the report will be valued and after receiving the approval of the costs\', "Comment 29: we will proceed to implement the changes.Could you please confirm if we can close this task?Regards\'", \'Comment 30: "I\\\'m waiting for user response..."]\']\nRelated Issues:\n[]\n\n### End'}
364	{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8668\n\n### Instruction:\nHi\r\n\r\nWe have some deliveries that expired after go live and DHP didn\'t locked these ones automatically.\r\nWe need to enter manually and block each one.\r\nFor example: FCP4431-S28\r\n\r\nCould you please check it?\r\n\r\nThank you very much\n\n### Response:\n["Comment 1: [\'!image!\'", \'Comment 2: "FYI:We already have this configuration set as true\', \'Comment 3: but it\\\'s not working!image-1!"\', "Comment 4: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", \'Comment 5: "{code:java}2023-03-01 00:15:30 (/Plant.Stock.BusinessLogic/BR-1-SV-VM0702/21920/46) [Error] Kotrak.Common.Infrastructure.IEventRunEnvironment - Error during Void Run[TimePassedEvent](Plant.Stock.BusinessLogic.Application.Interfaces.TimePassedEvent) methodSystem.AggregateException: One or more errors occurred. (Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \\\'Dispose\\\' on the context instance\', \'Comment 6: or wrapping it in a using statement. If you are using dependency injection\', "Comment 7: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'.) (Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance", \'Comment 8: or wrapping it in a using statement. If you are using dependency injection\', "Comment 9: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'.) (Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance", \'Comment 10: or wrapping it in a using statement. If you are using dependency injection\', "Comment 11: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'.) (Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance", \'Comment 12: or wrapping it in a using statement. If you are using dependency injection\', "Comment 13: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'.) (Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance", \'Comment 14: or wrapping it in a using statement. If you are using dependency injection\', "Comment 15: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'.) (Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance", \'Comment 16: or wrapping it in a using statement. If you are using dependency injection\', "Comment 17: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'.) (Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance", \'Comment 18: or wrapping it in a using statement. If you are using dependency injection\', "Comment 19: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'.) (Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance", \'Comment 20: or wrapping it in a using statement. If you are using dependency injection\', "Comment 21: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'.) (Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance", \'Comment 22: or wrapping it in a using statement. If you are using dependency injection\', "Comment 23: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'.) (Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance", \'Comment 24: or wrapping it in a using statement. If you are using dependency injection\', "Comment 25: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'.) (Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance", \'Comment 26: or wrapping it in a using statement. If you are using dependency injection\', "Comment 27: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'.) (Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance", \'Comment 28: or wrapping it in a using statement. If you are using dependency injection\', "Comment 29: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'.) (Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance", \'Comment 30: or wrapping it in a using statement. If you are using dependency injection\', "Comment 31: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'.) (Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance", \'Comment 32: or wrapping it in a using statement. If you are using dependency injection\', "Comment 33: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'.) (Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance", \'Comment 34: or wrapping it in a using statement. If you are using dependency injection\', "Comment 35: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'.) (Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance", \'Comment 36: or wrapping it in a using statement. If you are using dependency injection\', "Comment 37: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'.) (Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance", \'Comment 38: or wrapping it in a using statement. If you are using dependency injection\', "Comment 39: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'.) (Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance", \'Comment 40: or wrapping it in a using statement. If you are using dependency injection\', "Comment 41: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'.) (Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance", \'Comment 42: or wrapping it in a using statement. If you are using dependency injection\', "Comment 43: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'.) (Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance", \'Comment 44: or wrapping it in a using statement. If you are using dependency injection\', "Comment 45: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'.) (Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance", \'Comment 46: or wrapping it in a using statement. If you are using dependency injection\', "Comment 47: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'.) (Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance", \'Comment 48: or wrapping it in a using statement. If you are using dependency injection\', "Comment 49: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'.) (Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance", \'Comment 50: or wrapping it in a using statement. If you are using dependency injection\', "Comment 51: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'.) (Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance", \'Comment 52: or wrapping it in a using statement. If you are using dependency injection\', "Comment 53: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'.) (Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance", \'Comment 54: or wrapping it in a using statement. If you are using dependency injection\', "Comment 55: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'.) (Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance", \'Comment 56: or wrapping it in a using statement. If you are using dependency injection\', "Comment 57: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'.) (Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance", \'Comment 58: or wrapping it in a using statement. If you are using dependency injection\', "Comment 59: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'.) (Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance", \'Comment 60: or wrapping it in a using statement. If you are using dependency injection\', "Comment 61: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'.) (Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance", \'Comment 62: or wrapping it in a using statement. If you are using dependency injection\', "Comment 63: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'.) (Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance", \'Comment 64: or wrapping it in a using statement. If you are using dependency injection\', "Comment 65: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'.) (Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance", \'Comment 66: or wrapping it in a using statement. If you are using dependency injection\', "Comment 67: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'.) (Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance", \'Comment 68: or wrapping it in a using statement. If you are using dependency injection\', "Comment 69: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'.) (Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance", \'Comment 70: or wrapping it in a using statement. If you are using dependency injection\', "Comment 71: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'.) (Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance", \'Comment 72: or wrapping it in a using statement. If you are using dependency injection\', "Comment 73: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'.) (Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance", \'Comment 74: or wrapping it in a using statement. If you are using dependency injection\', "Comment 75: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'.) (Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance", \'Comment 76: or wrapping it in a using statement. If you are using dependency injection\', "Comment 77: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'.) (Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance", \'Comment 78: or wrapping it in a using statement. If you are using dependency injection\', "Comment 79: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'.) (Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance", \'Comment 80: or wrapping it in a using statement. If you are using dependency injection\', "Comment 81: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'.) (Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance", \'Comment 82: or wrapping it in a using statement. If you are using dependency injection\', "Comment 83: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'.) (Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance", \'Comment 84: or wrapping it in a using statement. If you are using dependency injection\', "Comment 85: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'.) (Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance", \'Comment 86: or wrapping it in a using statement. If you are using dependency injection\', "Comment 87: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'.) (Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance", \'Comment 88: or wrapping it in a using statement. If you are using dependency injection\', "Comment 89: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'.) (Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance", \'Comment 90: or wrapping it in a using statement. If you are using dependency injection\', "Comment 91: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'.) (Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance", \'Comment 92: or wrapping it in a using statement. If you are using dependency injection\', "Comment 93: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'.) (Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance", \'Comment 94: or wrapping it in a using statement. If you are using dependency injection\', "Comment 95: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'.) (Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance", \'Comment 96: or wrapping it in a using statement. If you are using dependency injection\', "Comment 97: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'.) (Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance", \'Comment 98: or wrapping it in a using statement. If you are using dependency injection\', "Comment 99: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'.) (Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance", \'Comment 100: or wrapping it in a using statement. If you are using dependency injection\', "Comment 101: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'.) (Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance", \'Comment 102: or wrapping it in a using statement. If you are using dependency injection\', "Comment 103: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'.) (Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance", \'Comment 104: or wrapping it in a using statement. If you are using dependency injection\', "Comment 105: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'.) (Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance", \'Comment 106: or wrapping it in a using statement. If you are using dependency injection\', "Comment 107: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'.) (Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance", \'Comment 108: or wrapping it in a using statement. If you are using dependency injection\', "Comment 109: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'.) (Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance", \'Comment 110: or wrapping it in a using statement. If you are using dependency injection\', "Comment 111: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'.) (Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance", \'Comment 112: or wrapping it in a using statement. If you are using dependency injection\', "Comment 113: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'.) (Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance", \'Comment 114: or wrapping it in a using statement. If you are using dependency injection\', "Comment 115: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'.) ---> System.ObjectDisposedException: Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance", \'Comment 116: or wrapping it in a using statement. If you are using dependency injection\', "Comment 117: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'. at Microsoft.EntityFrameworkCore.DbContext.CheckDisposed() at Microsoft.EntityFrameworkCore.DbContext.get_Database() at Kotrak.Common.Infrastructure.EF.TransactionEf..ctor(DbContext dbContext", \'Comment 118: DbContext eventContext\', "Comment 119: IsolationLevel isolationLevel) at Plant.Stock.BusinessLogic.Infrastructure.Factories.TransactionFactory.CreateTransaction() in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\99f3ad74a1ed56c8\\\\\\\\Plant.Stock.BusinessLogic\\\\\\\\Infrastructure\\\\\\\\Factories\\\\\\\\TransactionFactory.cs:line 23 at Plant.Stock.BusinessLogic.Application.Deliveries.Events.DeliveryExpirationByTimePassedEventHandler.Handle(TimePassedEvent event) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\99f3ad74a1ed56c8\\\\\\\\Plant.Stock.BusinessLogic\\\\\\\\Application\\\\\\\\Deliveries\\\\\\\\Events\\\\\\\\DeliveryExpirationByTimePassedEventHandler.cs:line 45 --- End of inner exception stack trace --- at Plant.Stock.BusinessLogic.Application.Deliveries.Events.DeliveryExpirationByTimePassedEventHandler.Handle(TimePassedEvent event) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\99f3ad74a1ed56c8\\\\\\\\Plant.Stock.BusinessLogic\\\\\\\\Application\\\\\\\\Deliveries\\\\\\\\Events\\\\\\\\DeliveryExpirationByTimePassedEventHandler.cs:line 60 at Kotrak.Common.Infrastructure.Events.EventEnvironment.Run[TEvent](TEvent event) at Castle.DynamicProxy.AbstractInvocation.Proceed() at Kotrak.Common.Infrastructure.Interceptors.LoggingInterceptor`1.Intercept(IInvocation invocation) ---> (Inner Exception #1) System.ObjectDisposedException: Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance", \'Comment 120: or wrapping it in a using statement. If you are using dependency injection\', \'Comment 121: you should let the dependency injection container take care of disposing context instances.Object name: \\\'StockContext\\\'.{code}"\', \'Comment 122: "I cała impreza od początku:{code:java}---> (Inner Exception #54) System.ObjectDisposedException: Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \\\'Dispose\\\' on the context instance\', \'Comment 123: or wrapping it in a using statement. If you are using dependency injection\', "Comment 124: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'. at Microsoft.EntityFrameworkCore.DbContext.CheckDisposed() at Microsoft.EntityFrameworkCore.DbContext.get_Database() at Kotrak.Common.Infrastructure.EF.TransactionEf..ctor(DbContext dbContext", \'Comment 125: DbContext eventContext\', "Comment 126: IsolationLevel isolationLevel) at Plant.Stock.BusinessLogic.Infrastructure.Factories.TransactionFactory.CreateTransaction() in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\99f3ad74a1ed56c8\\\\\\\\Plant.Stock.BusinessLogic\\\\\\\\Infrastructure\\\\\\\\Factories\\\\\\\\TransactionFactory.cs:line 23 at Plant.Stock.BusinessLogic.Application.Deliveries.Events.DeliveryExpirationByTimePassedEventHandler.Handle(TimePassedEvent event) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\99f3ad74a1ed56c8\\\\\\\\Plant.Stock.BusinessLogic\\\\\\\\Application\\\\\\\\Deliveries\\\\\\\\Events\\\\\\\\DeliveryExpirationByTimePassedEventHandler.cs:line 45<---2023-03-01 00:15:30 (/Plant.Stock.BusinessLogic/BR-1-SV-VM0702/21920/46) [Error] Plant.Stock.BusinessLogic.Infrastructure.Tasks.TimeIsPassingByTask - TimeIsPassingByTask exceptionSystem.AggregateException: One or more errors occurred. (Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance", \'Comment 127: or wrapping it in a using statement. If you are using dependency injection\', "Comment 128: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'.) (Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance", \'Comment 129: or wrapping it in a using statement. If you are using dependency injection\', "Comment 130: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'.) (Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance", \'Comment 131: or wrapping it in a using statement. If you are using dependency injection\', "Comment 132: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'.) (Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance", \'Comment 133: or wrapping it in a using statement. If you are using dependency injection\', "Comment 134: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'.) (Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance", \'Comment 135: or wrapping it in a using statement. If you are using dependency injection\', "Comment 136: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'.) (Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance", \'Comment 137: or wrapping it in a using statement. If you are using dependency injection\', "Comment 138: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'.) (Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance", \'Comment 139: or wrapping it in a using statement. If you are using dependency injection\', "Comment 140: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'.) (Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance", \'Comment 141: or wrapping it in a using statement. If you are using dependency injection\', "Comment 142: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'.) (Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance", \'Comment 143: or wrapping it in a using statement. If you are using dependency injection\', "Comment 144: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'.) (Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance", \'Comment 145: or wrapping it in a using statement. If you are using dependency injection\', "Comment 146: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'.) (Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance", \'Comment 147: or wrapping it in a using statement. If you are using dependency injection\', "Comment 148: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'.) (Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance", \'Comment 149: or wrapping it in a using statement. If you are using dependency injection\', "Comment 150: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'.) (Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance", \'Comment 151: or wrapping it in a using statement. If you are using dependency injection\', "Comment 152: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'.) (Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance", \'Comment 153: or wrapping it in a using statement. If you are using dependency injection\', "Comment 154: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'.) (Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance", \'Comment 155: or wrapping it in a using statement. If you are using dependency injection\', "Comment 156: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'.) (Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance", \'Comment 157: or wrapping it in a using statement. If you are using dependency injection\', "Comment 158: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'.) (Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance", \'Comment 159: or wrapping it in a using statement. If you are using dependency injection\', "Comment 160: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'.) (Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance", \'Comment 161: or wrapping it in a using statement. If you are using dependency injection\', "Comment 162: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'.) (Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance", \'Comment 163: or wrapping it in a using statement. If you are using dependency injection\', "Comment 164: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'.) (Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance", \'Comment 165: or wrapping it in a using statement. If you are using dependency injection\', "Comment 166: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'.) (Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance", \'Comment 167: or wrapping it in a using statement. If you are using dependency injection\', "Comment 168: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'.) (Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance", \'Comment 169: or wrapping it in a using statement. If you are using dependency injection\', "Comment 170: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'.) (Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance", \'Comment 171: or wrapping it in a using statement. If you are using dependency injection\', "Comment 172: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'.) (Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance", \'Comment 173: or wrapping it in a using statement. If you are using dependency injection\', "Comment 174: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'.) (Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance", \'Comment 175: or wrapping it in a using statement. If you are using dependency injection\', "Comment 176: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'.) (Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance", \'Comment 177: or wrapping it in a using statement. If you are using dependency injection\', "Comment 178: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'.) (Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance", \'Comment 179: or wrapping it in a using statement. If you are using dependency injection\', "Comment 180: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'.) (Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance", \'Comment 181: or wrapping it in a using statement. If you are using dependency injection\', "Comment 182: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'.) (Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance", \'Comment 183: or wrapping it in a using statement. If you are using dependency injection\', "Comment 184: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'.) (Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance", \'Comment 185: or wrapping it in a using statement. If you are using dependency injection\', "Comment 186: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'.) (Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance", \'Comment 187: or wrapping it in a using statement. If you are using dependency injection\', "Comment 188: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'.) (Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance", \'Comment 189: or wrapping it in a using statement. If you are using dependency injection\', "Comment 190: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'.) (Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance", \'Comment 191: or wrapping it in a using statement. If you are using dependency injection\', "Comment 192: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'.) (Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance", \'Comment 193: or wrapping it in a using statement. If you are using dependency injection\', "Comment 194: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'.) (Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance", \'Comment 195: or wrapping it in a using statement. If you are using dependency injection\', "Comment 196: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'.) (Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance", \'Comment 197: or wrapping it in a using statement. If you are using dependency injection\', "Comment 198: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'.) (Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance", \'Comment 199: or wrapping it in a using statement. If you are using dependency injection\', "Comment 200: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'.) (Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance", \'Comment 201: or wrapping it in a using statement. If you are using dependency injection\', "Comment 202: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'.) (Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance", \'Comment 203: or wrapping it in a using statement. If you are using dependency injection\', "Comment 204: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'.) (Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance", \'Comment 205: or wrapping it in a using statement. If you are using dependency injection\', "Comment 206: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'.) (Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance", \'Comment 207: or wrapping it in a using statement. If you are using dependency injection\', "Comment 208: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'.) (Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance", \'Comment 209: or wrapping it in a using statement. If you are using dependency injection\', "Comment 210: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'.) (Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance", \'Comment 211: or wrapping it in a using statement. If you are using dependency injection\', "Comment 212: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'.) (Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance", \'Comment 213: or wrapping it in a using statement. If you are using dependency injection\', "Comment 214: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'.) (Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance", \'Comment 215: or wrapping it in a using statement. If you are using dependency injection\', "Comment 216: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'.) (Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance", \'Comment 217: or wrapping it in a using statement. If you are using dependency injection\', "Comment 218: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'.) (Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance", \'Comment 219: or wrapping it in a using statement. If you are using dependency injection\', "Comment 220: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'.) (Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance", \'Comment 221: or wrapping it in a using statement. If you are using dependency injection\', "Comment 222: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'.) (Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance", \'Comment 223: or wrapping it in a using statement. If you are using dependency injection\', "Comment 224: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'.) (Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance", \'Comment 225: or wrapping it in a using statement. If you are using dependency injection\', "Comment 226: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'.) (Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance", \'Comment 227: or wrapping it in a using statement. If you are using dependency injection\', "Comment 228: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'.) (Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance", \'Comment 229: or wrapping it in a using statement. If you are using dependency injection\', "Comment 230: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'.) (Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance", \'Comment 231: or wrapping it in a using statement. If you are using dependency injection\', "Comment 232: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'.) (Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance", \'Comment 233: or wrapping it in a using statement. If you are using dependency injection\', "Comment 234: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'.) (Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance", \'Comment 235: or wrapping it in a using statement. If you are using dependency injection\', "Comment 236: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'.) ---> System.ObjectDisposedException: Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance", \'Comment 237: or wrapping it in a using statement. If you are using dependency injection\', "Comment 238: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'. at Microsoft.EntityFrameworkCore.DbContext.CheckDisposed() at Microsoft.EntityFrameworkCore.DbContext.get_Database() at Kotrak.Common.Infrastructure.EF.TransactionEf..ctor(DbContext dbContext", \'Comment 239: DbContext eventContext\', "Comment 240: IsolationLevel isolationLevel) at Plant.Stock.BusinessLogic.Infrastructure.Factories.TransactionFactory.CreateTransaction() in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\99f3ad74a1ed56c8\\\\\\\\Plant.Stock.BusinessLogic\\\\\\\\Infrastructure\\\\\\\\Factories\\\\\\\\TransactionFactory.cs:line 23 at Plant.Stock.BusinessLogic.Application.Deliveries.Events.DeliveryExpirationByTimePassedEventHandler.Handle(TimePassedEvent event) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\99f3ad74a1ed56c8\\\\\\\\Plant.Stock.BusinessLogic\\\\\\\\Application\\\\\\\\Deliveries\\\\\\\\Events\\\\\\\\DeliveryExpirationByTimePassedEventHandler.cs:line 45 --- End of inner exception stack trace --- at Plant.Stock.BusinessLogic.Application.Deliveries.Events.DeliveryExpirationByTimePassedEventHandler.Handle(TimePassedEvent event) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\99f3ad74a1ed56c8\\\\\\\\Plant.Stock.BusinessLogic\\\\\\\\Application\\\\\\\\Deliveries\\\\\\\\Events\\\\\\\\DeliveryExpirationByTimePassedEventHandler.cs:line 60 at Kotrak.Common.Infrastructure.Events.EventEnvironment.Run[TEvent](TEvent event) at Castle.DynamicProxy.AbstractInvocation.Proceed() at Kotrak.Common.Infrastructure.Interceptors.LoggingInterceptor`1.Intercept(IInvocation invocation) at Castle.DynamicProxy.AbstractInvocation.Proceed() at Castle.Proxies.IEventRunEnvironmentProxy.Run[TCommand](TCommand command) at Plant.Stock.BusinessLogic.Infrastructure.Tasks.TimeIsPassingByTask.<ExecuteAsync>b__9_0() in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\99f3ad74a1ed56c8\\\\\\\\Plant.Stock.BusinessLogic\\\\\\\\Infrastructure\\\\\\\\Tasks\\\\\\\\TimeIsPassingByTask.cs:line 41 ---> (Inner Exception #1) System.ObjectDisposedException: Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \'Dispose\' on the context instance", \'Comment 241: or wrapping it in a using statement. If you are using dependency injection\', "Comment 242: you should let the dependency injection container take care of disposing context instances.Object name: \'StockContext\'. at Microsoft.EntityFrameworkCore.DbContext.CheckDisposed() at Microsoft.EntityFrameworkCore.DbContext.get_Database() at Kotrak.Common.Infrastructure.EF.TransactionEf..ctor(DbContext dbContext", \'Comment 243: DbContext eventContext\', \'Comment 244: IsolationLevel isolationLevel) at Plant.Stock.BusinessLogic.Infrastructure.Factories.TransactionFactory.CreateTransaction() in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\99f3ad74a1ed56c8\\\\\\\\Plant.Stock.BusinessLogic\\\\\\\\Infrastructure\\\\\\\\Factories\\\\\\\\TransactionFactory.cs:line 23 at Plant.Stock.BusinessLogic.Application.Deliveries.Events.DeliveryExpirationByTimePassedEventHandler.Handle(TimePassedEvent event) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\99f3ad74a1ed56c8\\\\\\\\Plant.Stock.BusinessLogic\\\\\\\\Application\\\\\\\\Deliveries\\\\\\\\Events\\\\\\\\DeliveryExpirationByTimePassedEventHandler.cs:line 45<---{code}"\', "Comment 245: \'W appsettings jest wporzo!image-2023-03-02-09-09-44-345.png!\'", "Comment 246: \'Na naszym środowisku (170) SU/dostawy też nie są automatycznie lockowane. Pojawiają się te same błedy. Zgłosiłam DAP-13382.\'", "Comment 247: \'[[email protected]]u nas na teście też nie działa", "Comment 248: Olcia sprawdziła :P\'", "Comment 249: \'Dzięki Olcia <3\'", "Comment 250: \'Please be informed that we have forwarded the issue to the development team in order to internal analysis.We are waiting for more details and will be back with further information as soon as possible.\'", "Comment 251: \'[[email protected]] nie do końca niestety z tego co wiem. Jak drugi imp będzie zrealizowany to powiemy że jest działa.Wtedy napiszemy im w której wersji release 8.5 jest to poprawione.\'", "Comment 252: \'[[email protected]]a teraz co im przekazać? jutro będą pewnie pytać\'", "Comment 253: \'Hi,This will be fixed in new version of DHP. For more details", "Comment 254: please contact Marcin Kleszcz.Regards\'", \'Comment 255: "Hi [[email protected]]Thanks for this information. However other versions already have this functionality and this is having a huge impact for the factory and warehouse management. We can\\\'t wait for next version release! We don\\\'t have an estimated date yet.Dear [[email protected]] do you now which version is this fixed? 8.6? When will it get ready for release?Thank you"\', "Comment 256: \'Hi [[email protected]]as I understood Maciej well", "Comment 257: this will be a fix deployed to the current 8.5 version. [[email protected]]could you please provide more detailed feedback?\'", "Comment 258: \'[[email protected]] odpiszesz mu coś albo skontaktujesz się z nim mailowo czy cóś? :)\'", \'Comment 259: "Hi [[email protected]]yes\', \'Comment 260: this fix was done to the latest 8.5.Currently we are working on GDC\\\'s for 8.5 version (2_3weeks).We can deploy versios with fix for Expiry together with changes from GDC\\\'s?"\', \'Comment 261: "Hi [[email protected]]I\\\'m relieved! I thought the new version of DHP would be 8.6ThanksHi [[email protected]]Is there any chance to update this fix sooner?Thank you very much!"\', \'Comment 262: "Hi [[email protected]]yes\', "Comment 263: I discussed with [[email protected]] and version will be ready at the beginning of next week - with GDC\'s.Please create a DGS to make an estimation.I guess Maicon", \'Comment 264: first we need to update RC Test. When you will approved\', \'Comment 265: we can plan an update on RC Prod?"\', "Comment 266: \'[[email protected]]DGS-8727 was created to update GDC_2-3weeksThank you for the instructions.[[email protected]] you can close this taskThank you very much!\'", "Comment 267: \'Thank you [[email protected]]\']"]\nRelated Issues:\n[\'DGS-8683\', \'DAP-13382\', \'DAP-13384\']\n\n### End'}
365	{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8667\n\n### Instruction:\nHello,\r\n\r\nwe noticed for lot reports of packed goods, like Z20 variant, we got wrong lot reports in the ERP. We checked 0061270223024 from location Nijkerk, and we see 3 messages in the communication to the ERP: But as it seems, the first message that is processed is incorrect, with as produced item the bulk code, and as consumed item also the bulk code. Because of this the packed product is not added to ERP stock. Can you check from DHC side what messages are send to ERP for lot 0061270223024?\n\n### Response:\n[\'Comment 1: ["Hello @servicedesk\', "Comment 2: I\'ve discussed this already with Przemek", \'Comment 3: so ticket is for him to analyse and book hours\', \'Comment 4: thanks!"\', "Comment 5: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.I am sending this task to Przemek.RegardsAgnieszka Januszewska\'", \'Comment 6: \\\'<s:Header> <Action s:mustUnderstand="1" xmlns="http://schemas.microsoft.com/ws/2005/05/addressing/none">unit01_dhc_adapter_ws_provider_wsd_webMethods_DHC_Provider_Binder_insertProductionLotReport</Action> </s:Header> <s:Body xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema"> <insertProductionLotReport xmlns="http://deheus.com/unit01/DHC"> <input xmlns=""> <header> <ReceivingSystem>Milas</ReceivingSystem> <SendingSystem>DHC</SendingSystem> <CreateDate>2023-02-27T14:03:15.17</CreateDate> <CreateUser xsi:nil="true" /> <MessageID>3de88d0c-6088-43bb-a42a-c4cd91fcae93</MessageID> </header> <productionLotReport> <ProductionOrderReference>0061270223024</ProductionOrderReference> <ProducedItem>169900</ProducedItem> <ProducedQTY>2400.01</ProducedQTY> <ProducedQTYUOM>kg</ProducedQTYUOM> <Plant>6</Plant> <ProductionDateTime>2023-02-27T14:03:15.17</ProductionDateTime> <ProductionLotTypeIndicator>9</ProductionLotTypeIndicator> </productionLotReport> </input> </insertProductionLotReport> </s:Body></s:Envelope>\\\'\', \'Comment 7: \\\'<s:Header> <Action s:mustUnderstand="1" xmlns="http://schemas.microsoft.com/ws/2005/05/addressing/none">unit01_dhc_adapter_ws_provider_wsd_webMethods_DHC_Provider_Binder_insertProductionLotReport</Action> </s:Header> <s:Body xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema"> <insertProductionLotReport xmlns="http://deheus.com/unit01/DHC"> <input xmlns=""> <header> <ReceivingSystem>Milas</ReceivingSystem> <SendingSystem>DHC</SendingSystem> <CreateDate>2023-02-27T14:03:15.17</CreateDate> <CreateUser xsi:nil="true" /> <MessageID>7da1ab4c-7545-4c9f-bc1c-bce61e50bb3a</MessageID> </header> <productionLotReport> <ProductionOrderReference>0061270223024</ProductionOrderReference> <ProducedItem>169900-Z20</ProducedItem> <ProducedQTY>2400.01</ProducedQTY> <ProducedQTYUOM>kg</ProducedQTYUOM> <Plant>6</Plant> <ProductionDateTime>2023-02-27T14:03:15.17</ProductionDateTime> <ProductionLotTypeIndicator>1</ProductionLotTypeIndicator> <Lines> <ItemCode>169900</ItemCode> <ConsumedQTY>2400</ConsumedQTY> <ConsumedQTYUOM>KG</ConsumedQTYUOM> </Lines> </productionLotReport> </input> </insertProductionLotReport> </s:Body></s:Envelope>\\\'\', \'Comment 8: "Hi [[email protected]]indeed at the begining are received draft PLR which was designed for starlims so it send Recipes (DHH bulk item). Also it was said during AS400 decommissioning project that its\\\' enough because you were planing to use only bulk products for those factories. I you would like to change it to use also packed products then we will need to make change in data communication. If you agree to such a change then please create GDC and we will estimate this change for you."\', "Comment 9: \'GDC-886 created", "Comment 10: ticket can be closed\'", "Comment 11: \'Thank you.\']"]\nRelated Issues:\n[]\n\n### End'}
366	{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8666\n\n### Instruction:\nPlease remove add tech VH303514\n\n### Response:\n["Comment 1: [\'!afbeelding!\'", "Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", "Comment 3: \'id technologii w plancie08E5D177-3FB2-4DC3-8A6E-DCAA8E569296\'", "Comment 4: \'Hello", \'Comment 5: Can I ask why tan technology should be removed. It was added in September 2022 and more than 600 PRL were created from it. When deleting technologies\', \'Comment 6: we also remove PRL documents from several bases for DHP and DHC moduls\', \'Comment 7: but as a rule\', "Comment 8: they were single objects.\'", \'Comment 9: "Select --DELETE SFROM Recipes XLEFT JOIN ProductionLots P ON X.Id = P.RecipeIdLEFT JOIN DHPlantStockBusinessLogicMain.dbo.ProductionLots S ON S.Id = P.IdWHERE X.ItemId=\\\'9BA8FD4E-4CDF-4F2A-94C7-B59D629D70B2\\\' and Version=0to daje jakies 669 lotów"\', "Comment 10: \'Hi agnieska", \'Comment 11: I understand but this is an excellent example of why we need a archive functionaliity: This additional technology is made by mistake by someone from our formulation department. He/she did not inform IT so the technology stays in the system and lot reports are made: Lot reports coming from this produce and consume the same item as you can see in the tech\', "Comment 12: so I gues you can call it a ghost technology because it doesnt do anything besides creating useless lot reports\'", "Comment 13: \'Ok I need to contact with dev for addituonal analisys", \'Comment 14: cause beacuse this PRL were created since 2022 I do not want to make anyinconsistency of data resulting from such actions from the database side. As for new functionality\', "Comment 15: please make such a GDc task if such a replacement if not priced.\'", \'Comment 16: "select from ProductionLotReports where technologyid=\\\'D9FE29AB-3E5D-44C2-B542-20A7B65BE3B2\\\'( dhc service)"\', "Comment 17: \'@Agnieszka", \'Comment 18: I have planned a meeting Tuesday with Maciej\', "Comment 19: Thomas and me to discuss this. Maciej told me you can stop spamming him about this subject :)\'", \'Comment 20: "Wrzucam skrypt sql do naprawienia archiwizacji receptury z product definition po stronie modułu PCS\', \'Comment 21: dla wersji R8.5:{code:sql}-- DGS-8666\', "Comment 22: R8.5 workaround for product definition recipe archivization-- Set @RecipeId to desired guidDECLARE @RecipeId UNIQUEIDENTIFIER = \'00000000-0000-0000-0000-000000000000\';DECLARE @RecipeEntityId INT = (SELECT r.EntityId FROM dbo.Recipes r WHERE r.Id = @RecipeId);UPDATE dbo.Recipes\\\\tSET IsProductDefinition = 0WHERE Id = @RecipeId;DELETE FROM dbo.ExportRecipesWHERE EntityId = @RecipeEntityId;INSERT INTO dbo.ExportRecipes (PackageId", \'Comment 23: SendDate\', \'Comment 24: ConfirmDate\', \'Comment 25: ExternalSystemId\', \'Comment 26: EntityId)SELECT NEWID()\', \'Comment 27: GETDATE()\', \'Comment 28: GETDATE()\', \'Comment 29: er.Id\', \'Comment 30: r.EntityIdFROM dbo.Recipes rJOIN dbo.ExternalSystems er ON 1 = 1WHERE r.Id = @RecipeId;{code}Skrypt można też znaleźć w repozytoriach:[[link]\|http://10.10.10.52:82/projects/PLA3/repos/dhp30implementations/browse/BASE/8.5.0/SQL/PCS_RecipeArchivizationWorkaround.sql]"\', "Comment 31: \'!image-2023-03-13-13-37-15-336.png!!image-2023-03-13-13-36-52-410.png!\'", "Comment 32: \'W PCS nie ma receptury", \'Comment 33: więc luz\', "Comment 34: pozostaje zmienić ProductDefinition = 0 w DHC i Service!image-2023-03-13-14-00-03-761.png!\'", "Comment 35: \'Hi,Additional TechnologyVH303514 has been prevented from sending to PCS and from another use in DHC.Regards\'", \'Comment 36: "Po konsultacji z Łukaszem jeszcze:update [DHPlantProdBusinessLogicMain].dbo.Recipes set IsProductDefinition = 0 --where Id = \\\'08E5D177-3FB2-4DC3-8A6E-DCAA8E569296\\\'"\', "Comment 37: \'Thanks you can close the ticket\']"]\nRelated Issues:\n[]\n\n### End'}
367	{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8665\n\n### Instruction:\nZgłaszam problem z algorytmem umów 3*33 miesięcy. Przy wprowadzeniu danych dot. PPK nie mogę zapisać aktualizacji danych u pracownika Justyna Gąsiorowska. Pracownica ma umowę na czas nieokreślony od 01.09.2022.\r\n\r\nProszę o sprawdzenie poprawności działania algorytmu.\n\n### Response:\n["Comment 1: [\'!image!\'", "Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", "Comment 3: \'Istnieją zapisy na czas nieokreślony z brakiem końcowej daty : !screenshot-1! To jest przyczyna błędu\'", "Comment 4: \'Paulina przekazała mi", "Comment 5: że nie jest w stanie wprowadzić/uzupełnić tych zapisów - czy jesteśmy w stanie wyłączyć tą blokadę by mogła je uzupełnić? Lub czy jesteś w stanie je uzupełnić jeżeli Paulina poda mi poprawne dane ? \'", "Comment 6: \'Hi", "Comment 7: You can temporaily disable below trigger to fill missing data. !screenshot-2! \'", \'Comment 8: "Ok\', \'Comment 9: that\\\'s works - task to close."]\']\nRelated Issues:\n[]\n\n### End'}
368	{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8664\n\n### Instruction:\nHi,\r\n\r\nShipping Notice L000145524 isn\'t arriving in DHC. Also its orders SO000076185, SOBE000015497 and SOBE000015612 are not arriving.\r\nThey are succesfully processed according to the Communication Log, but I can\'t find them within the orders in DHC.\r\n\r\nCan you please check?\n\n### Response:\n["Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", "Comment 2: \'Dear Theo,For what plant are mentioned Orders?Regards\'", "Comment 3: \'Those two are in DHC now", "Comment 4: checking the third one!image-2023-03-01-14-06-15-080.png!!image-2023-03-01-14-06-48-094.png!\'", "Comment 5: \'For what item wasSOBE000015612 and the shipping notice?\'", "Comment 6: \'Hi Aleksandra", "Comment 7: SOBE000015612 was for item 303225. I will export it again from ERP\'", "Comment 8: \'The plant was VeghelOnly see your question now\'", "Comment 9: \'Thank you\'", "Comment 10: \'Yes", "Comment 11: I have asked few questions :)\'", "Comment 12: \'I see that the other order is blocked by our ERP", "Comment 13: so I think that we can downgrade this one to P3 and I even think we can close it already but I like to have the confirmation from our business first.Many thanks again Aleksandra!\'", "Comment 14: \'!image-2023-03-01-14-55-25-330.png!!image-2023-03-01-14-55-43-804.png!\'", "Comment 15: \'Dla Orderów są dwa mapowania", "Comment 16: i te dwa są już w DHC!image-2023-03-01-14-59-48-967.png!\'", "Comment 17: \'Nie ma kolejek!image-2023-03-01-15-02-21-095.png!!image-2023-03-01-15-02-45-780.png!\'", "Comment 18: \'Dear Theo,And what about Shipping Notice? I can see it is mapped with DHC. Is it blocked as well? Waiting for the confirmation from Business then\'", \'Comment 19: "I guess the planner has cancelled the shipping notices as the orders are not planned anymore. Let\\\'s close the task :)"\', "Comment 20: \'Sure. Thank you.Have a nice afternoon :)\'", "Comment 21: \'Indeed tey are cancelled :) !image-2023-03-01-15-40-16-730.png!\']"]\nRelated Issues:\n[]\n\n### End'}
369	{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8663\n\n### Instruction:\nHi\r\n\r\nWe have some recipes approved and released from BESTMIX this morning, but they are not integrating to DHC.\r\nWe are trying to open DHH application but it closes automatically when loading the auth screen.\r\n\r\nCould you please help us? We have urgent recipes to accept on DHC and start production.\r\n\r\nNone of attached recipes is on DHC.\r\n\r\nThank you\n\n### Response:\n["Comment 1: [\'!MicrosoftTeams-image (47)!!MicrosoftTeams-image (48)!\'", "Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", "Comment 3: \'DHH utraciło połaczenie z serwerem bazy danych i się zawiesiło około godziny 11:30", "Comment 4: o 13:33 uruchomiłem wszystko ponownie.\'", "Comment 5: \'DHH the connection from the database server dropped and hung", "Comment 6: resolved by developers.\'", "Comment 7: \'please check.\'", "Comment 8: \'Hi PiotrNow we can access DHH and see that the Recipes are there.However they are not in DHC yet. I can imagine that we need to wait the integration time from DHH to DHC", "Comment 9: right?Thank you very much!image!\'", "Comment 10: \'We are still verifying this issue.\'", "Comment 11: \' !screenshot-1! Recipes are processing.\'", "Comment 12: \'Hi PiotrNow we can see recipes on DHC. You can close this task.Thank you very much!\']"]\nRelated Issues:\n[]\n\n### End'}
370	{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8662\n\n### Instruction:\nHi,\r\n\r\nI am trying to create additional purchase costs, however, I cannot attach PORI-documents. Please assist\n\n### Response:\n["Comment 1: [\'!image!\'", "Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", "Comment 3: \'Could you please specify - send more and full screenshoots from function you start to use. Did you try to use more then one document? If yes please provide numbers.\'", "Comment 4: \'RegardsHello,We are closing this task as we haven’treceivedany replyfromyouforalong time. If the issueappearsagain", "Comment 5: please raise another task.BRAgnieszka Januszewska\'", "Comment 6: \'hi i wish to open this ticket\'", "Comment 7: \'!image-1!\'", "Comment 8: \'!image-2!!image-3!\'", "Comment 9: \'we cant add IPOR of Deliveries to the additional purchase cost\']"]\nRelated Issues:\n[]\n\n### End'}
371	{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8661\n\n### Instruction:\nCould you please give access to Intense for [email protected]?\r\n\r\nFarach Nadirov is her full name and she is replacing Janine Schellekens.\n\n### Response:\n["Comment 1: [\'Hi,[[email protected]],Janine has been added in test and prod Intense environment.She can feel free to test log in.Best regards,Grzegorz\'", "Comment 2: \'Farach is as well?\'", "Comment 3: \'Yes", "Comment 4: Farach :).\'", "Comment 5: \'Can be closed.\'", \'Comment 6: "I\\\'m closing task.Best regards,Grzegorz"]\']\nRelated Issues:\n[]\n\n### End'}
372	{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8660\n\n### Instruction:\nPORs processed through Johnson DHP donot generate automatically unless i maually generate them in DHC. Help provide a permanent solution please.\n\n### Response:\n["Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", "Comment 2: \'Lista dokumentów do wygenerowania w DHC bez informacji o błędach,konfiguracja jest !screenshot-2! próba przesłania ręcznie działa - np. 4/3/2023/JN,5/3/2023/JNte z rana do błędy z erpintegratora przy pierwszej próbie:Vehicle Ticket with number 4/3/2023/JN has 0 elements - SKIPPED! !screenshot-1! \'", "Comment 3: \'Hej", \'Comment 4: potrzebowalibyśmy wsparcia w temacie\', \'Comment 5: erpintegrator ma problem z generowaniem dokumentów z VT dla planta ze zgłoszenia \', "Comment 6: z ręki się generują z poziomu dhc.\\\\rBłąd jaki jest to:\\\\r Vehicle Ticket with number 4/3/2023/JN has 0 elements - SKIPPED!\'", "Comment 7: \'DHCService dzieli VT na header i elementy.Najpierw przychodzi header i dodawany jest wpis do VehicleTicketForProcessingA później elementy.Erp integrator pobiera VT", \'Comment 8: które mają wpis w VehicleTicketForProcessing\', \'Comment 9: jak nie ma elementów\', "Comment 10: to usuwa wpis z VehicleTicketForProcessing i pomija VT.Dodałem fix i czekam na CR\'", "Comment 11: \'Hello", "Comment 12: our developers have determined the cause.I will let you know in this task.\'", "Comment 13: \'okay\'", "Comment 14: \'Michał Kordys zrobił fixa", "Comment 15: pytanie jak to będzie rozwiązane jako release czy hotfixem. \\\\rKlient dopytuje o termin i samą realizację.\\\\rAndrzej Roszak może ustalić termin z klientem.\'", "Comment 16: \'Hello", "Comment 17: ERP Integrator 3.46.0will include this fix.\'", "Comment 18: \'okay sir", "Comment 19: thank you.please close\']"]\nRelated Issues:\n[]\n\n### End'}
373	{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8659\n\n### Instruction:\nPlease help to check PLR 43710270223003 in CanTho Plant ( 0437) .\r\n\r\nProduction lot number 43710270223003 has item 6101607 consumes 5336,1 kg .But check on "item history" or "Delivery tracking" item 6101607 is releasing a difference quatity.\n\n### Response:\n["Comment 1: [\'!image!!image-1!!image-2!\'", "Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", "Comment 3: \'Whether the password to the admin account has been changed? standard does not authorize access. For plant Can Tho.\'", "Comment 4: \'i just reset the password: XNeu3R14RE. you can try to set password to standard \'", \'Comment 5: "Na plr się nie zgadza ilość z zasobu jest większa o kod 437-S007JJ{code:java}SELECT [Created] ,[AggregateType] ,[Event] ,[EventType] ,[UserName] ,[CorrelationId] FROM [DHPlantProdBusinessLogicEvents].[dbo].[ProductionLots] where AggregateId=\\\'a7eedd33-4de8-4aab-b3dd-3c3cc3d71edd\\\' --and Event like \\\'%5688%\\\' order by Created{code}{code:java} SELECT [Created] ,[Event] ,[EventType] ,[UserName] ,[CorrelationId] FROM [DHPlantStockBusinessLogicEvents].[dbo].[StockUnits] where AggregateId=\\\'F8DB1F99-6875-4CB7-9984-E8D94F815B41\\\' order by Created{code}robił realizację PLR jeden user - TAJI !screenshot-1! StockUnits:9FBAEBC6-4C3B-47DC-B848-DEC2F2CB42915EDFD54D-904D-4104-827F-882E79B42F9E1F8F2E0C-86B3-4CBC-AF01-40579DB824DEF8DB1F99-6875-4CB7-9984-E8D94F815B41{code:java} FROM [DHPlantStockBusinessLogicMain].[dbo].[StockUnits] where barcode=\\\'437-S007JJ\\\' or Barcode=\\\'437-S007G1\\\' or Barcode=\\\'437-S007H0\\\' or Barcode=\\\'437-S007I4\\\'{code}!image-2023-03-03-12-12-45-405!"\', "Comment 6: \'Hej", \'Comment 7: ustalenia stand up\', "Comment 8: proszę o pomoc w analizie - dzięki.\'", "Comment 9: \'[[email protected]]To jeszcze przydałyby się backupy DB: prod (main", \'Comment 10: events\', \'Comment 11: intercontext) oraz stock (main\', \'Comment 12: events\', \'Comment 13: intercontext).Jeżeli backupów się nie da załatwić\', \'Comment 14: to proszę o instrukcję\', "Comment 15: jak się dobrać do baz na tym środowisku.W przeciwnym razie nie mam jak rozpocząć jakiejkolwiek analizy.\'", "Comment 16: \'[[email protected]]Backupy baz https://cloud.kotrak.com/index.php/s/kqXGwgLBp9tQP2p\'", "Comment 17: \'[[email protected]] Dzięki wielkie :)Wrzucam plik z wynikiem analizy: [^analysis.txt] W wielkim skrócie zaszły 4 operacje: # PLR został utworzony (status Created) na 15000 kg # Następnie zaszła próba potwierdzenia", \'Comment 18: ale się nie udało\', \'Comment 19: bo zabrakło stanu dla jednego z surowców (pozakładały się rezerwacje na tyle na ile mogły\', \'Comment 20: prawdopodobnie po FIFO) # Następnie zaszła edycja ilości\', \'Comment 21: na nagłówku na 15960 kg\', \'Comment 22: rezerwacje zaktualizowały się na tyle\', \'Comment 23: na ile mogły (tu już brakowało stanu dla dwóch surowców\', \'Comment 24: ale to nie było potwierdzanie PLR) # Na koniec zaszło udane potwierdzenie PLR\', \'Comment 25: ale ze zmienionymi ilościami\', \'Comment 26: na nagłówku na 14520 kg - coś tu się pokićkało przy rozliczaniu PLRa i się zużyło 352.8 kg jednego z surowców za dużoPatrząc w kod źródłowy\', \'Comment 27: to trochę ciężko wywnioskować dokładnie gdzie jest problem\', \'Comment 28: ale w każdym razie coś w StockEngine nie do końca dobrze aktualizuje rezerwacje\', \'Comment 29: możliwe że ma to związek z tymi ciągłymi zmianami ilości\', \'Comment 30: najpierw w górę\', \'Comment 31: a potem - przy potwierdzaniu - w dół. Ciężko też stwierdzić\', \'Comment 32: dlaczego ten błąd zaszedł tylko dla tego jednego\', \'Comment 33: konkretnego surowca.[[email protected]] Może nasze asy QA byłyby w stanie wyklikać taki przypadek na którymś z naszych środowisk? Byłoby o wiele prościej dojść do tego\', \'Comment 34: gdzie dokładnie leży problem. Tyle że to jest R8.3. Wstępnie wydaje mi się\', \'Comment 35: że zaczyna się to [podczas rezerwowania SU zaraz przed potwierdzaniem PLR\|http://10.10.10.52:82/projects/PLA3/repos/plant.stock.businesslogic/browse/Plant.Stock.BusinessLogic/Application/ProductionLots/ProductionLotService.cs?at=refs%2Fheads%2Fmaster#455]\', \'Comment 36: podczas [wyliczania różnic między aktualnymi rezerwacjami a porządanymi\|http://10.10.10.52:82/projects/PLA3/repos/plant.stock.businesslogic/browse/Plant.Stock.BusinessLogic/Domain/Services/ReservationDomainService.cs?at=refs%2Fheads%2Fmaster#198]. Ciężko też powiedzieć\', \'Comment 37: czy w R8.5 jest to naprawione\', "Comment 38: w każdym razie [różnic jest dość sporo\|http://10.10.10.52:82/projects/PLA3/repos/plant.stock.businesslogic/compare/diff?targetBranch=refs%2Fheads%2Fmaster&sourceBranch=refs%2Fheads%2Frelease%2FMV20_R8.5&targetRepoId=539#Plant.Stock.BusinessLogic/Application/ProductionLots/ProductionLotService.cs]. Wrzucam również pełną historię zmian tego PLR: [^Aggregate_A7EEDD334DE84AABB3DD3C3CC3D71EDD_20230309T092113.txt] Oraz historię zmian każdej z tych czterech opisanych wyżej operacji: # [^Correlation_E8615A1F405C4520BEC3C64B2699B7DD_20230309T121033.txt] # [^Correlation_CF09CD9C7B824C0D84EC8D322ABA2958_20230309T122525.txt] # [^Correlation_F9C198B09EAB48CFBDA24FD7069C7DAF_20230309T133531.txt] # [^Correlation_C7A7B177F08F44ACBB9894F77637964D_20230309T093641.txt] \']"]\nRelated Issues:\n[]\n\n### End'}
374	{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8658\n\n### Instruction:\nThe mentioned document does not appear in the database for exchange (CDNPS_Exchange) between comarch and mpp (invoicing program).\r\n\r\n\n\n### Response:\n["Comment 1: [\'!image!\'", "Comment 2: \'Kindly approve lowering priority of this task to P2 as P1 issues are only those with a critical or a blocking impact on business processes This seems not to be the case in this issue so we suggest decreasing the issue priority.Regards\'", "Comment 3: \'OK", "Comment 4: you can decrease priority to P2.\'", "Comment 5: \'!image-2023-03-01-11-37-40-994.png!\'", "Comment 6: \'2023-03-01 08:00:52,426 [14] INFO - Handled poison message after error. Original conversation ID=\\\\\'5d3186cb-feb7-ed11-8154-00155d030305\\\\\'", "Comment 7: error conversation ID=\\\\\'5e3186cb-feb7-ed11-8154-00155d030305\\\\\'", "Comment 8: error queue name \\\\\'CDN.TradeInvoiceQueue\\\\\'.2023-03-01 08:00:52,426 [14] INFO - Handled poison message after error. Original conversation ID=\\\\\'5d3186cb-feb7-ed11-8154-00155d030305\\\\\'", "Comment 9: error conversation ID=\\\\\'5e3186cb-feb7-ed11-8154-00155d030305\\\\\'", \'Comment 10: error queue name \\\\\\\'CDN.TradeInvoiceQueue\\\\\\\'.2023-03-01 08:00:52,426 [14] ERROR - Exception occurred when executing task Bookkeeping.Exchange.TradeInvoices.TradeInvoicesSynchronizationTask.\\\\\\\\{"EntityValidationErrors": [ "0": { "Entity": "Bookkeeping.Exchange.TradeInvoices.TradeInvoice"\', \'Comment 11: "ValidationErrors": [ {"PropertyName": "Description"\', \'Comment 12: "ErrorMessage": "The field Description must be a string or array type with a maximum length of \\\\\\\'200\\\\\\\'."} ] }C:\\\\\\\\Applications\\\\\\\\Bookkeeping.Service\\\\\\\\Logs\\\'\', "Comment 13: \'HelloI checked the log in synchronization service and structure of the [CDNPS_Exchange] database and the reason why this document was not synchronized is to long description!image-2023-03-01-12-01-51-924.png!It has 260 characters when system and database allowed max 200.I may change the description from database lelvel in erp xl.Let me know how I may change the description.!image-2023-03-01-12-01-51-924!\'", "Comment 14: \'Leave only the first EI complete. EI-2/02/23/CUEOn all others", "Comment 15: remove EI- and CUE from the name.\'", \'Comment 16: "trngidnumer=1688385update cdn.trnopisyset TnO_Opis=\\\'Popust 1% za rano placanje\', \'Comment 17: EI-2/02/23/CUE\', \'Comment 18: 5/02/23\', \'Comment 19: 6/02/23\', \'Comment 20: 9/02/23\', \'Comment 21: 12/02/23\', \'Comment 22: 15/02/23\', \'Comment 23: 16/02/23\', \'Comment 24: 22/02/23\', \'Comment 25: 24/02/23\', \'Comment 26: 25/02/23\', \'Comment 27: 26/02/23\', \'Comment 28: 29/02/23\', \'Comment 29: 32/02/23\', \'Comment 30: 35/02/23\\\'where TnO_TrnNumer=1688385"\', "Comment 31: \'Please verify\'", "Comment 32: \'Still not resolved. Can you check the Exchange db because it appears that is still not synced with our invoicing application?\'", "Comment 33: \'Hello please verify again right know it is in the exchange db!image-2023-03-01-16-09-48-091.png!\'", "Comment 34: \'Now it is OK. Thank you.\']"]\nRelated Issues:\n[]\n\n### End'}
375	{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8657\n\n### Instruction:\nGood morning,\r\n\r\nwe have got on problem on DHC.\r\nPlease could you help us.\r\nThis is urgent while we also had an update on DHP location Maasbracht this morning.\r\n\r\nKind regards,\r\n\r\nGerard Geerts\n\n### Response:\n["Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", "Comment 2: \'Hello,Synchronization is working for now", \'Comment 3: please check.DHC Service now processes messages.There is a very large queue for reprocessing\', "Comment 4: I will be back with information for you Regards\'", "Comment 5: \'!image-2023-03-01-09-03-42-472.png!\'", "Comment 6: \'Goodmorning Adrian,thanks for your support.Hopefully you can tell us about the problem.Regards,Gerard\'", "Comment 7: \'{code:java}2023-02-28 19:46:52,983 [10] INFO Evolution.BusinessPlatform.Applications.PlatformApplication [(null)] - Application Evolution.DHCService.PlatformApplication has been stopped!2023-02-28 19:47:53,858 [6] INFO Evolution.BusinessPlatform.Applications.PlatformApplication [(null)] - Starting application: Evolution.DHCService.PlatformApplication2023-02-28 19:47:53,858 [6] INFO Evolution.BusinessPlatform.Applications.PlatformApplication [(null)] - Checking application Evolution.DHCService.PlatformApplication manifest file2023-02-28 19:48:00,967 [10] INFO Evolution.BusinessPlatform.Applications.PlatformApplication [(null)] - Application Evolution.DHCService.PlatformApplication is running!2023-03-01 08:30:55,035 [4] INFO Evolution.BusinessPlatform.Applications.PlatformApplication [(null)] - Stopping application Evolution.DHCService.PlatformApplication2023-03-01 08:30:55,035 [4] INFO Evolution.BusinessPlatform.Applications.PlatformApplication [(null)] - Application Evolution.DHCService.PlatformApplication has been stopped!2023-03-01 08:34:21,888 [7] INFO Evolution.BusinessPlatform.Applications.PlatformApplication [(null)] - Starting application: Evolution.DHCService.PlatformApplication2023-03-01 08:34:21,888 [7] INFO Evolution.BusinessPlatform.Applications.PlatformApplication [(null)] - Checking application Evolution.DHCService.PlatformApplication manifest file2023-03-01 08:34:28,982 [10] INFO Evolution.BusinessPlatform.Applications.PlatformApplication [(null)] - Application Evolution.DHCService.PlatformApplication is running!2023-03-01 08:39:23,114 [7] INFO Evolution.BusinessPlatform.Applications.PlatformApplication [(null)] - Stopping application Evolution.DHCService.PlatformApplication2023-03-01 08:39:23,114 [7] INFO Evolution.BusinessPlatform.Applications.PlatformApplication [(null)] - Application Evolution.DHCService.PlatformApplication has been stopped!2023-03-01 08:43:11,165 [5] INFO Evolution.BusinessPlatform.Applications.PlatformApplication [(null)] - Starting application: Evolution.DHCService.PlatformApplication2023-03-01 08:43:11,165 [5] INFO Evolution.BusinessPlatform.Applications.PlatformApplication [(null)] - Checking application Evolution.DHCService.PlatformApplication manifest file2023-03-01 08:43:18,274 [4] INFO Evolution.BusinessPlatform.Applications.PlatformApplication [(null)] - Application Evolution.DHCService.PlatformApplication is running!2023-03-01 08:49:18,470 [7] INFO Evolution.BusinessPlatform.Applications.PlatformApplication [(null)] - Stopping application Evolution.DHCService.PlatformApplication2023-03-01 08:49:18,470 [7] INFO Evolution.BusinessPlatform.Applications.PlatformApplication [(null)] - Application Evolution.DHCService.PlatformApplication has been stopped!2023-03-01 08:52:19,995 [7] INFO Evolution.BusinessPlatform.Applications.PlatformApplication [(null)] - Starting application: Evolution.DHCService.PlatformApplication2023-03-01 08:52:19,995 [7] INFO Evolution.BusinessPlatform.Applications.PlatformApplication [(null)] - Checking application Evolution.DHCService.PlatformApplication manifest file2023-03-01 08:52:27,090 [5] INFO Evolution.BusinessPlatform.Applications.PlatformApplication [(null)] - Application Evolution.DHCService.PlatformApplication is running!2023-03-01 08:58:15,672 [7] INFO Evolution.BusinessPlatform.Applications.PlatformApplication [(null)] - Stopping application Evolution.DHCService.PlatformApplication2023-03-01 08:58:15,672 [7] INFO Evolution.BusinessPlatform.Applications.PlatformApplication [(null)] - Application Evolution.DHCService.PlatformApplication has been stopped!2023-03-01 08:58:19,690 [6] INFO Evolution.BusinessPlatform.Applications.PlatformApplication [(null)] - Starting application: Evolution.DHCService.PlatformApplication2023-03-01 08:58:19,690 [6] INFO Evolution.BusinessPlatform.Applications.PlatformApplication [(null)] - Checking application Evolution.DHCService.PlatformApplication manifest file2023-03-01 08:58:26,750 [4] INFO Evolution.BusinessPlatform.Applications.PlatformApplication [(null)] - Application Evolution.DHCService.PlatformApplication is running!2023-03-01 09:37:03,345 [4] INFO Evolution.BusinessPlatform.Applications.PlatformApplication [(null)] - Stopping application Evolution.DHCService.PlatformApplication2023-03-01 09:37:03,345 [4] INFO Evolution.BusinessPlatform.Applications.PlatformApplication [(null)] - Application Evolution.DHCService.PlatformApplication has been stopped!2023-03-01 09:38:42,780 [4] INFO Evolution.BusinessPlatform.Applications.PlatformApplication [(null)] - Starting application: Evolution.DHCService.PlatformApplication2023-03-01 09:38:42,780 [4] INFO Evolution.BusinessPlatform.Applications.PlatformApplication [(null)] - Checking application Evolution.DHCService.PlatformApplication manifest file2023-03-01 09:38:49,890 [7] INFO Evolution.BusinessPlatform.Applications.PlatformApplication [(null)] - Application Evolution.DHCService.PlatformApplication is running!2023-03-01 09:52:35,535 [6] INFO Evolution.BusinessPlatform.Applications.PlatformApplication [(null)] - Stopping application Evolution.DHCService.PlatformApplication2023-03-01 09:52:35,535 [6] INFO Evolution.BusinessPlatform.Applications.PlatformApplication [(null)] - Application Evolution.DHCService.PlatformApplication has been stopped!2023-03-01 09:54:10,826 [5] INFO Evolution.BusinessPlatform.Applications.PlatformApplication [(null)] - Starting application: Evolution.DHCService.PlatformApplication2023-03-01 09:54:10,826 [5] INFO Evolution.BusinessPlatform.Applications.PlatformApplication [(null)] - Checking application Evolution.DHCService.PlatformApplication manifest file2023-03-01 09:54:17,950 [4] INFO Evolution.BusinessPlatform.Applications.PlatformApplication [(null)] - Application Evolution.DHCService.PlatformApplication is running!2023-03-01 10:05:09,197 [10] INFO Evolution.BusinessPlatform.Applications.PlatformApplication [(null)] - Stopping application Evolution.DHCService.PlatformApplication2023-03-01 10:05:09,197 [10] INFO Evolution.BusinessPlatform.Applications.PlatformApplication [(null)] - Application Evolution.DHCService.PlatformApplication has been stopped!2023-03-01 10:06:43,522 [4] INFO Evolution.BusinessPlatform.Applications.PlatformApplication [(null)] - Starting application: Evolution.DHCService.PlatformApplication2023-03-01 10:06:43,522 [4] INFO Evolution.BusinessPlatform.Applications.PlatformApplication [(null)] - Checking application Evolution.DHCService.PlatformApplication manifest file2023-03-01 10:06:50,615 [10] INFO Evolution.BusinessPlatform.Applications.PlatformApplication [(null)] - Application Evolution.DHCService.PlatformApplication is running!{code}\'", "Comment 8: \'Of course", \'Comment 9: The application looped the process\', "Comment 10: restarting the service solved the situation.So there is still processing on the application.See screen!image-2023-03-01-10-32-42-264.png\|width=455,height=268!I will come back to you with the information once all the news has been reprocessed.\'", "Comment 11: \'HelloBack to you with the informationprocessing of the message has been completed !image-2023-03-01-13-07-41-286.png!Should i close your incident or do you need more informations? The problem has been resolved? Regards\'", "Comment 12: \'Good morning Adrian,the problem has been resolved.Thanks for feedback and support on this.Please close this serviceticket.Kind regards,Gerard\']"]\nRelated Issues:\n[]\n\n### End'}
376	{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8656\n\n### Instruction:\nHi\r\n\r\nWe have VT-594/23 released for intake. The user complained that after performing ACCEPT action during bulk VT intake system was too slow, presented a message of error ("Contact system admin") and now the VT has the wrong Total weight value.\r\nThe right value for Total weight is 28040\r\nWe don\'t have option to reverse IsAccepted status, and no option to fix the right value.\r\nAlso, when we try to COMPLETE the VT with the wrong value, a message "Contact system admin" is displayed\r\n\r\nCould you please fix that?\r\n\r\nThank you very much\n\n### Response:\n["Comment 1: [\'!image!\'", "Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", \'Comment 3: \\\'id:97141CDE-9641-4CE4-BE03-6292DBBBDBACNoooo poleciał timeoucik{code:java}2023-02-22 15:53:51 (8a5ef721-446b-4347-9e29-b9f6b77196a0/Plant.VC.BusinessLogic/BR-4-SV-VM0204/19260/205) [Error] Microsoft.EntityFrameworkCore.Query - An exception occurred while iterating over the results of a query for context type \\\\\\\'"Plant.VC.BusinessLogic.Infrastructure.EF.VCContext"\\\\\\\'."""Microsoft.Data.SqlClient.SqlException (0x80131904): Execution Timeout Expired. The timeout period elapsed prior to completion of the operation or the server is not responding. ---> System.ComponentModel.Win32Exception (258): The wait operation timed out. at Microsoft.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj\', \'Comment 4: Boolean callerHasConnectionLock\', \'Comment 5: Boolean asyncClose) at Microsoft.Data.SqlClient.TdsParserStateObject.ThrowExceptionAndWarning(Boolean callerHasConnectionLock\', \'Comment 6: Boolean asyncClose) at Microsoft.Data.SqlClient.TdsParserStateObject.ReadSniError(TdsParserStateObject stateObj\', \'Comment 7: UInt32 error) at Microsoft.Data.SqlClient.TdsParserStateObject.ReadSniSyncOverAsync() at Microsoft.Data.SqlClient.TdsParserStateObject.TryReadNetworkPacket() at Microsoft.Data.SqlClient.TdsParserStateObject.TryPrepareBuffer() at Microsoft.Data.SqlClient.TdsParserStateObject.TryReadByte(Byte& value) at Microsoft.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior\', \'Comment 8: SqlCommand cmdHandler\', \'Comment 9: SqlDataReader dataStream\', \'Comment 10: BulkCopySimpleResultSet bulkCopyHandler\', \'Comment 11: TdsParserStateObject stateObj\', \'Comment 12: Boolean& dataReady) at Microsoft.Data.SqlClient.SqlDataReader.TryConsumeMetaData() at Microsoft.Data.SqlClient.SqlDataReader.get_MetaData() at Microsoft.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds\', \'Comment 13: RunBehavior runBehavior\', \'Comment 14: String resetOptionsString\', \'Comment 15: Boolean isInternal\', \'Comment 16: Boolean forDescribeParameterEncryption\', \'Comment 17: Boolean shouldCacheForAlwaysEncrypted) at Microsoft.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior\', \'Comment 18: RunBehavior runBehavior\', \'Comment 19: Boolean returnStream\', \'Comment 20: Boolean isAsync\', \'Comment 21: Int32 timeout\', \'Comment 22: Task& task\', \'Comment 23: Boolean asyncWrite\', \'Comment 24: Boolean inRetry\', \'Comment 25: SqlDataReader ds\', \'Comment 26: Boolean describeParameterEncryptionRequest) at Microsoft.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior\', \'Comment 27: RunBehavior runBehavior\', \'Comment 28: Boolean returnStream\', \'Comment 29: TaskCompletionSource`1 completion\', \'Comment 30: Int32 timeout\', \'Comment 31: Task& task\', \'Comment 32: Boolean& usedCache\', \'Comment 33: Boolean asyncWrite\', \'Comment 34: Boolean inRetry\', \'Comment 35: String method) at Microsoft.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior) at Microsoft.Data.SqlClient.SqlCommand.ExecuteDbDataReader(CommandBehavior behavior) at Microsoft.EntityFrameworkCore.Storage.RelationalCommand.ExecuteReader(RelationalCommandParameterObject parameterObject) at Microsoft.EntityFrameworkCore.Query.Internal.SingleQueryingEnumerable`1.Enumerator.InitializeReader(Enumerator enumerator) at Microsoft.EntityFrameworkCore.SqlServer.Storage.Internal.SqlServerExecutionStrategy.Execute[TState,TResult](TState state\', \'Comment 36: Func`3 operation\', \'Comment 37: Func`3 verifySucceeded) at Microsoft.EntityFrameworkCore.Query.Internal.SingleQueryingEnumerable`1.Enumerator.MoveNext()ClientConnectionId:23c5c591-641f-46b4-aa72-aab9f18ba26eError Number:-2,State:0,Class:11"Microsoft.Data.SqlClient.SqlException (0x80131904): Execution Timeout Expired. The timeout period elapsed prior to completion of the operation or the server is not responding. ---> System.ComponentModel.Win32Exception (258): The wait operation timed out. at Microsoft.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj\', \'Comment 38: Boolean callerHasConnectionLock\', \'Comment 39: Boolean asyncClose) at Microsoft.Data.SqlClient.TdsParserStateObject.ThrowExceptionAndWarning(Boolean callerHasConnectionLock\', \'Comment 40: Boolean asyncClose) at Microsoft.Data.SqlClient.TdsParserStateObject.ReadSniError(TdsParserStateObject stateObj\', \'Comment 41: UInt32 error) at Microsoft.Data.SqlClient.TdsParserStateObject.ReadSniSyncOverAsync() at Microsoft.Data.SqlClient.TdsParserStateObject.TryReadNetworkPacket() at Microsoft.Data.SqlClient.TdsParserStateObject.TryPrepareBuffer() at Microsoft.Data.SqlClient.TdsParserStateObject.TryReadByte(Byte& value) at Microsoft.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior\', \'Comment 42: SqlCommand cmdHandler\', \'Comment 43: SqlDataReader dataStream\', \'Comment 44: BulkCopySimpleResultSet bulkCopyHandler\', \'Comment 45: TdsParserStateObject stateObj\', \'Comment 46: Boolean& dataReady) at Microsoft.Data.SqlClient.SqlDataReader.TryConsumeMetaData() at Microsoft.Data.SqlClient.SqlDataReader.get_MetaData() at Microsoft.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds\', \'Comment 47: RunBehavior runBehavior\', \'Comment 48: String resetOptionsString\', \'Comment 49: Boolean isInternal\', \'Comment 50: Boolean forDescribeParameterEncryption\', \'Comment 51: Boolean shouldCacheForAlwaysEncrypted) at Microsoft.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior\', \'Comment 52: RunBehavior runBehavior\', \'Comment 53: Boolean returnStream\', \'Comment 54: Boolean isAsync\', \'Comment 55: Int32 timeout\', \'Comment 56: Task& task\', \'Comment 57: Boolean asyncWrite\', \'Comment 58: Boolean inRetry\', \'Comment 59: SqlDataReader ds\', \'Comment 60: Boolean describeParameterEncryptionRequest) at Microsoft.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior\', \'Comment 61: RunBehavior runBehavior\', \'Comment 62: Boolean returnStream\', \'Comment 63: TaskCompletionSource`1 completion\', \'Comment 64: Int32 timeout\', \'Comment 65: Task& task\', \'Comment 66: Boolean& usedCache\', \'Comment 67: Boolean asyncWrite\', \'Comment 68: Boolean inRetry\', \'Comment 69: String method) at Microsoft.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior) at Microsoft.Data.SqlClient.SqlCommand.ExecuteDbDataReader(CommandBehavior behavior) at Microsoft.EntityFrameworkCore.Storage.RelationalCommand.ExecuteReader(RelationalCommandParameterObject parameterObject) at Microsoft.EntityFrameworkCore.Query.Internal.SingleQueryingEnumerable`1.Enumerator.InitializeReader(Enumerator enumerator) at Microsoft.EntityFrameworkCore.SqlServer.Storage.Internal.SqlServerExecutionStrategy.Execute[TState,TResult](TState state\', \'Comment 70: Func`3 operation\', \'Comment 71: Func`3 verifySucceeded) at Microsoft.EntityFrameworkCore.Query.Internal.SingleQueryingEnumerable`1.Enumerator.MoveNext()ClientConnectionId:23c5c591-641f-46b4-aa72-aab9f18ba26eError Number:-2,State:0,Class:112023-02-22 21:00:11 (/Plant.VC.BusinessLogic/BR-4-SV-VM0204/19260/9) [Error] Microsoft.EntityFrameworkCore.Database.Command - Failed executing DbCommand ("0"ms) [Parameters=[""]\', "Comment 72: CommandType=\\\\\'Text\\\\\'", \'Comment 73: CommandTimeout=\\\\\\\'30\\\\\\\']"""SELECT TOP 0 T.[Id] INTO [dbo].[InboundMessagesTempdfc59f5f] FROM [dbo].[InboundMessages] AS T LEFT JOIN [dbo].[InboundMessages] AS Source ON 1 = 0;"2023-02-22 21:00:46 (/Plant.VC.BusinessLogic/BR-4-SV-VM0204/19260/9) [Error] Microsoft.EntityFrameworkCore.Database.Command - Failed executing DbCommand ("0"ms) [Parameters=[""]\', "Comment 74: CommandType=\\\\\'Text\\\\\'", \'Comment 75: CommandTimeout=\\\\\\\'30\\\\\\\']"""SELECT TOP 0 T.[Id] INTO [dbo].[InboundMessagesTemp9dc27413] FROM [dbo].[InboundMessages] AS T LEFT JOIN [dbo].[InboundMessages] AS Source ON 1 = 0;"{code}\\\'\', "Comment 76: \'!image-2023-03-01-08-25-17-358.png!!image-2023-03-01-08-50-14-982.png!!image-2023-03-01-08-50-14-982!\'", "Comment 77: \'Dear Maicon,I think better option would be cancel this vt as it is in progress and create a new one. Please", "Comment 78: let me know if it is fine for you.Regards!image-2023-03-01-10-44-47-073.png!\'", "Comment 79: \'Hi AleksandraIf we cancel his VT", \'Comment 80: the new one will generate a new SU barcode\', \'Comment 81: right?We cannot cancel current SU barcode because the user already scanned it on PCS. And the consumption already started for it.Unless you keep the current SU barcode for the new VT document\', "Comment 82: OK we could do it.Thank you\'", "Comment 83: \'Hi Maicon,Why are users scanning barcode and start consumption before VT is not copleted?Please", \'Comment 84: check now\', "Comment 85: you should complete itRegards\'", \'Comment 86: "Hi AleksandraThey used because we had this issue on DHP and they couldn\\\'t wait for the fix and started using it.When we click COMPLETE button\', \'Comment 87: the message appears.[:\\\'(]!image-1!"\', "Comment 88: \'Please", "Comment 89: try again\'", "Comment 90: \'Hi Aleksandra Now I was able to close it.You can close this task.Thank you very much!\'", "Comment 91: \'Thank you\']"]\nRelated Issues:\n[]\n\n### End'}
377	{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8655\n\n### Instruction:\n This warehouse order should have had the status Executed\r\n\r\nVT has been closed.\r\nstatus of warehouse order then should be Executed\r\n\r\nwhat was going on here and can you change the status to Executed?\n\n### Response:\n["Comment 1: [\'!image-3!!image-4!\'", "Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", "Comment 3: \'[[DHP 3.0]Incorrect WO status\|onenote:https://kotrak.sharepoint.com/sites/erpasysta/Shared%20Documents/Baza%20wiedzy/Baza%20Wiedzy%20-%20ERPSD/Klienci/DEHEUS/DEHEUS%20APPLICATIONS/RPA/Baza%20wiedzy.one#%5bDHP%203.0%5dIncorrect%20WO%20status&section-id=\\\\\\\\{A2F09CD6-A23A-42F3-92F5-ED66B521455B}&page-id=\\\\\\\\{325B9921-0AB5-4E36-A871-095DF356E2F1}&end] ([Widok sieci Web\|https://kotrak.sharepoint.com/sites/erpasysta/_layouts/OneNote.aspx?id=%2Fsites%2Ferpasysta%2FShared%20Documents%2FBaza%20wiedzy%2FBaza%20Wiedzy%20-%20ERPSD&wd=target%28Klienci%2FDEHEUS%2FDEHEUS%20APPLICATIONS%2FRPA%2FBaza%20wiedzy.one%7CA2F09CD6-A23A-42F3-92F5-ED66B521455B%2F%5BDHP%203.0%5DIncorrect%20WO%20status%7C325B9921-0AB5-4E36-A871-095DF356E2F1%2F%29])\'", "Comment 4: \'Status was fixed please verify!image-2023-02-28-19-48-33-363.png!\'", "Comment 5: \'I also check logs from the 9.01.2023 but could not see any error log.\'", "Comment 6: \'May we close the task?\'", "Comment 7: \'close the task\']"]\nRelated Issues:\n[]\n\n### End'}
378	{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8654\n\n### Instruction:\nHello,\r\n\r\nattached you find a list of lot report for which we miss the raw material consumptions in the ERP: It means that the quantity finished product is send, but after that the raw material consumption is not resend. Can you resend these lot reports from DHC. as there is no manual possibility to do this \n\n### Response:\n["Comment 1: [\'[^Missing lot reports in ERP.xlsx] _(284 kB)_\'", "Comment 2: \'Due to the financially year-end closing", "Comment 3: this has high prio\'", "Comment 4: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", "Comment 5: \'Dear,According to the service agreement this task should be categorized as a service request.Kindly approve change of the type of this task.Also this file include over 3000 plr", "Comment 6: it will be time consuming.For what date you need it to be resend? If it may wait until tomorrow pleaseapprove lowering priority of this task to P2 as P1 issues are only those with a critical or a blocking impact on business processes .BRAgnieszka Januszewska\'", \'Comment 7: "Hi Agnieska\', "Comment 8: it\'s unclear if this is a service request: if these reports are missing in the ERP/Integration layer", \'Comment 9: then it looks like they are not send\', \'Comment 10: hence being an application incident? Task can wait untill tomorrow\', \'Comment 11: but as said in the comment below\', \'Comment 12: due to the year-end closing over 2022 these reports are important and should be (re)send as soon as possible\', \'Comment 13: Agreed you can lower priority"\', "Comment 14: \'Total to be resend is around 1500: only those with DHP lot number should be resend (I tried to filter on that)\'", "Comment 15: \'Thank you.I asked Przemysław to help with that issue", "Comment 16: he will look at this tommorow.\'", "Comment 17: \'[[email protected]]byłabym wdzięczna jakbyś to im wysłał", "Comment 18: możesz się też odnieśc do koncepcji Thomasa że to nasza wina.\'", \'Comment 19: "[[email protected]]I\\\'ve resend lot reports that were correct\', \'Comment 20: in[^Missing PLRs.xlsx]I\\\'ve prepared list of lot reports that couldn\\\'t be send to ERP."\', \'Comment 21: "Hi [[email protected]]\', \'Comment 22: remaining PLR\\\'s (case with missing technologies elements) has been resent."\', "Comment 23: \'Thanks", "Comment 24: we can close this ticket\'", "Comment 25: \'Thank you\']"]\nRelated Issues:\n[]\n\n### End'}
379	{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8653\n\n### Instruction:\nWe need to know what our users did and caused this to happened. Namely in the time period 01.01.2023 until today some PLR (23.-24./02/2023 probably) has been confirmed but we are not sure if the materials are on stock after production because we have missing quantity for Item No. 10420300. The amount in CDN is 5666.73 kg and it misses 12753.27 kg more to close VTs which is 18420 kg in total. The same problem we had last year with the same item. Can you please check this? Thank you. \n\n### Response:\n["Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", "Comment 2: \'Please clarify", \'Comment 3: I checked the item from the pharmacy level in ERP XL no errors or reservations are shown\', \'Comment 4: what do I mean by "and it misses 12753.27" is this item physically in stock and not in the documents? I can see to vt not generatedI don\\\\\\\'t see such quantities or PLR in DHP either. On top of that the item given is a product not a material\', "Comment 5: so it is not consumed to handle other goods.In DHC all PRL are generated.So please be more specific.\'", \'Comment 6: "vte nie jest spiety z zadnym deliveryselect * from VehicleTickets vt join VehicleTicketElements ve on ve.VehicleTicketId=vt.id where DocumentNumber like \\\'572/2/2023%\\\'"\', "Comment 7: \'this item is already loaded and delivered to costumers. PLR is confirmed and also JO. i have checked every JO from beginning of the year and they are all in system. from some reason", "Comment 8: quantity for this item is not on stock in system.\'", "Comment 9: \'Do you need more info from Vukota or this is enough? Thanks.\'", "Comment 10: \'I so pierwtly verified if there are any discrepancies on the erp xl side. However", \'Comment 11: from the documents the status is correct. Currently\', "Comment 12: I see 2 SOR documents generated by another operator than ERPIntegrator for the amount of 5020 kg. SOR-1/01/23/SMSOR-2/01/23/SMWhich will cause a discrepancy between the comparison with documents created from dhc. Can I ask in what way you calculate the expected quantity ?Translated with www.DeepL.com/Translator (free version)\'", \'Comment 13: "select * from cdn.twrkarty where twr_kod =\\\'10420300\\\'select cdn.nazwaobiektu(trn_gidtyp,trn_gidnumer,1,2),TrN_OpeNumerW,tre_ilosc\', \'Comment 14: TrN_Stan,* from cdn.TraElem join cdn.TraNag on trn_gidnumer=tre_gidnumerwhere TrN_TrNRok>=2022 and tre_twrnumer=5211 and TrN_OpeNumerw<>13 and trn_gidtyp=2001select * from cdn.opekarty where ope_ident like \\\'erp%\\\' or ope_gidnumer=143"\', "Comment 15: \'in attachment VT`s which is stuck in DHC. when I add up these quantities that have been loaded and subtract the current balance in the program", "Comment 16: i get the difference that is missing from the balance.!Screenshot_11!\'", "Comment 17: \'1.In ERP XL checked with a special function the state of goods whether there is no shortage and possibly repair the state ( for example", "Comment 18: when some document is not damaged. In ERPXL there are no such errors for this commodity. 2. there are no stocks in DHC. 3. in ERP XL there are documents created from DHC and documents created by users - I gave an example.But for both VT I use generate options and there was error but after service restart I generated SORc for VT 562/2/2023!image-2023-03-08-10-57-59-184.png\|width=1117,height=275!For VT 572/2for s warehouse there are 3726 ,73 kg for sale in erp xl on warehouse S!image-2023-03-08-11-00-56-768.png![^image-2023-03-08-10-57-59-184.png]!image-2023-03-08-11-00-50-156! !image-2023-03-08-11-00-56-768!\'", "Comment 19: \'!562.PNG\|thumbnail! !draftplr.PNG\|thumbnail! !jonorders.PNG\|thumbnail!\'", "Comment 20: \'I also checked the since the 01.01.023 there is a lot of PRL in draft ( still not confirmed in DHP)So after confirm them in dhp", \'Comment 21: sending PLR for missing plr to dhc and dhp\', "Comment 22: the new delivery and IR+ document will be added.Also you may find in ERP XL Job Orders for that item that are not realized ( so the not new IR+ documents where created).So please verify what JO and PLR could be fullfield to create stocks for Item you are missing. !562.PNG!\'", "Comment 23: \'May we close the task?\'", "Comment 24: \'Hello,We are closing this task as we haven’treceivedany replyfromyouforalong time. If the issueappearsagain", "Comment 25: please raise another task.Regards\']"]\nRelated Issues:\n[]\n\n### End'}
380	{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8652\n\n### Instruction:\nWe have problem with xml, the information are genereated different, in attached I added some difference that I found. I sent the current format of xml but the lab not accept, the main problem is the code, should appear 178 but is showing LX178 on new xml.\r\nCould you fix it please?\r\n\n\n### Response:\n["Comment 1: [\'[^DHHIMP90000001.xml] _(2 kB)_!XML!!XML2!\'", "Comment 2: \'old format[^DHHIMP90008640.xml] _(3 kB)_\'", "Comment 3: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", "Comment 4: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", "Comment 5: \'Please be informed that we have forwarded the issue to the development team in order to internal analysis.We are waiting for more details and will be back with further information as soon as possible.Regards\'", "Comment 6: \'[[email protected]]chyba potrzebujemy wsparcia w tym temacie :)\'", "Comment 7: \'[[email protected]] dogrzebałam się to jakiegoś starego taska", \'Comment 8: w którym była informacja o sample type: "Sample Item Code (cutting-> only numbers\', \'Comment 9: NO LETTERS) DHP Item code- ONLY NUMBERS !!!".Sprawdziłam na 170 i dla itema LX110 w sample type pojawia się LX110\', "Comment 10: natomiast dla np. 7680OK-B10 jest poprawnie 768010. Zgłosiłam DAP-13380.\'", "Comment 11: \'[[email protected]]Ustalam z klientem jak dokładnie powinno to działać.\'", "Comment 12: \'[[email protected]]pewka\'", "Comment 13: \'Dear Priscyla,Could you please precise how it should work now?We found that for example for itemLX110", "Comment 14: in sample type we haveLX110,whereas for item7680OK-B10 we have correct768010.Regards\'", "Comment 15: \'Hi Aleksandra,I asked help for Bart and he explained the fields with problem are sampletype", \'Comment 16: should appear 178\', \'Comment 17: but is showing LX178\', "Comment 18: ArticleCode shoud appear 178 but is showing LX178 and the result should be with dot and is showing with comma. Could you fix it?Correct format:<sampletype>178</sampletype> <ArticleCode>178</ArticleCode><results> <code>VCRDRYI</code> <desc>Input DM weight in</desc> <val>214.75</val> <sign /> <date>2022-12-21</date> <cnct>0</cnct> </results>\'", "Comment 19: \'Thank you\'", \'Comment 20: \\\'[[email protected]] poza LX to jeszcze klient wspomina o "should be with dot and is showing with comma"\\\'\', "Comment 21: \'Rozmawiałem z [[email protected]] przekażemy ten temat do Theo niech on to ustali jak ma działać.\'", "Comment 22: \'Mebrate answer that one more field is wrong", "Comment 23: <CountryId>BR</CountryId> should be <CountryId>3</CountryId>Could you check this field too?\'", "Comment 24: \'ok\'", "Comment 25: \'@Priscyla", \'Comment 26: I suggest a short meeting with Bart Lunenburg from the lab\', \'Comment 27: Mebrate\', \'Comment 28: Sharlene from South Africa and perhaps Joost Jansens from the R&D department to discuss how to approach this.it is currently working form RSA and CZ and I am affraid if we change things for you\', "Comment 29: it impacts other Business Units as wellDo you agree?\'", "Comment 30: \'Hi Theo,yes", "Comment 31: I agree. Could you schedule the meeting?Thank you\'", \'Comment 32: "Hello GuysWe changed the configuration on QAM of country from string BR to number 3.We also requested to the operator to change its language from _pt-BR_ to _en-US_ when generating XML file.Let\\\'s see what happens.Thank you"\', \'Comment 33: "HiTest with country configuration and language setup on the operator UI profile did work!However I\\\'d like to know why the users\\\'s language preference is interfering with the XML generation. BLGG uses an international decimal separator!I see this as a bug on XML generation engine. Could you fix that\', \'Comment 34: please?Thank you"\', \'Comment 35: "Hi,we tested current format of XML and it\\\'s working automatically. So we don\\\'t need to change the <sampletype> and <ArticleCode>. The Country ID is fixed too.So now is missing only Maicon request about the needs to change language to create correct XML.Thank you"\', \'Comment 36: "Hi [[email protected]]Did you have time to check Priscyla\\\'s last comment?Thank you"\', "Comment 37: \'Dear Maicon,This task is under dev analysis so the most proper person to ask about the language change will by still [[email protected]]. So we are waiting for Dev Team feedback then.Regards\'", "Comment 38: \'Hi [[email protected]]We can confirm that language is being considered while generating decimal values for XML files.This issue needs to have a GDC ticket created", "Comment 39: but first I need to speak with Theo.I will inform you about the output of the discussion.\'", "Comment 40: \'Thank you very much!\'", "Comment 41: \'Hi [[email protected]],I created a GDC-900 to solve the issue with the generation of decimals values\']"]\nRelated Issues:\n[\'DAP-7671\', \'DAP-6810\', \'DAP-13380\']\n\n### End'}
381	{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8651\n\n### Instruction:\nProblems clipping SOR-155/09/2022 with SORC-218.09\r\n\r\nSOR-155 was on invoice 9/460/2022 as zero. The thought off the user was to remove it and then sor-155/09/2022 will come back in the list, but that was not the case\r\n\r\nAfter clicking OK the last screen was shown\n\n### Response:\n["Comment 1: [\'!image-2!!image-3!!image-4!!image-5!\'", "Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", "Comment 3: \'SOR-155/09/2022 is already clipped and booked at this document :!image-2023-02-28-17-44-49-607.png!Please try to cancel it (the clipped invoice) and then try agaian to creat clipped invoice\'", "Comment 4: \'!image!\'", "Comment 5: \'!relateddocs_1!\'", "Comment 6: \'HelloI see that the previous information was not clear I hope it will be clearer now.Invoice 460/09/2020 is cancelled.Previously I focused on SOR!image-2023-03-14-08-28-55-759.png\|width=830,height=121!When you are looking at the message you send there is an info :!image-2023-03-14-08-33-17-027.png!The source document for SORC 218/09 is the SOR 1551.If you want to created clip invoice for pair of SOR and SORCthe SORC in to be at this clipped source document SOR2. You can only use one time a SOR/SORC document on clipped invoiceSo because the SOR 155 is already clipped", \'Comment 7: when you are creating new clipped invoice it is skipped and then ERP XL is trying to create clip inoice only for SORC 218\', \'Comment 8: so you got this message.3. How to find related doucments on SOR\', "Comment 9: SORCThere is few way to see if SOR is clipped already- by related documents buttom!relateddocs_1.png! * on document header!image-2023-03-14-08-55-34-901.png!So today I verified again documents and situation Is still the same.The SOR 155/09/2022 is clipped with visible on screenshots invoice 512/09/2022And solution is still the same * cancell this invoice * create new clipp document\'", "Comment 10: \'Hello,We are closing this task as we haven’treceivedany replyfromyouforalong time. If the issueappearsagain", "Comment 11: please raise another task.Regards\']"]\nRelated Issues:\n[]\n\n### End'}
382	{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8650\n\n### Instruction:\nClippen SOR 29/10/2022 not working with SOR 26+27+28/10/2022\r\n\r\nThe VAT amount of € 771.75 is not included\n\n### Response:\n["Comment 1: [\'!image-2!!image-3!!image-4!\'", "Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", "Comment 3: \'!t2.PNG\|thumbnail!\'", "Comment 4: \'Reason for that situation is that in sor 29/9 there is diffrent value in that place:!t2.PNG!it should be the same in all documentsfor 27-29/10 we have type 21 - return of goods!image-2023-02-28-17-34-34-600.png!In that case you may clipped all the 3 sorc document", "Comment 5: Or if you ask we change them to type 11 via database.\'", "Comment 6: \'May we close the task?\'", "Comment 7: \'Hello,We are closing this task as we haven’treceivedany replyfromyouforalong time. If the issueappearsagain", "Comment 8: please raise another task.Regards\']"]\nRelated Issues:\n[]\n\n### End'}
383	{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8649\n\n### Instruction:\nThe report is not showing the correct quantity for orders. We have sales order for item SUP7159-T-S25 but the column for total sales order is empty.\r\nWe need this report working to schedule productions.\r\n\r\nCould you check, please?\r\n\r\nHi Maciej Dobrzański\r\nthe column Total ordered needs to show Total quantity of all order not checked by period, we need total integrated orders (without quantity loaded). In the column Order quantity for next days, system needs to consider quantity of days added inicially. So report is wrong, Could you fix it?\r\n\r\nWe notice that in column blocked system is adding reservation, is wrong too, reservation needs to be removed from Total ordered quantity and Order quantity for next days when VT is loaded. Could you fix this columns too?\r\n\r\nI attached the first request to explain better. We need to fix column blocked, total ordered, and Order for next days.\r\n(https://helpdesk.kotrak.com/browse/DHITS-722)\n\n### Response:\n["Comment 1: [\'!image-2023-02-25-10-32-54-598!!image-2023-02-25-10-33-58-694![^IMPROVEMENT – PRODUCTION V3.pdf] _(1,18 MB)_\'", "Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", "Comment 3: \'Do przetestowania w GDC\'", "Comment 4: \'!ItemsSummary!\'", "Comment 5: \'!44! !75! !105!!Items summary_fields!\'", \'Comment 6: \\\'Dear [[email protected]]1. "the column Total ordered needs to show Total quantity of all order not checked by period\', \'Comment 7: we need total integrated orders (without quantity loaded). In the column Order quantity for next days\', \'Comment 8: system needs to consider quantity of days added inicially. So report is wrong\', \'Comment 9: Could you fix it?"* please verify attached pictures from our tests on RC Prod server. Total ordered shows Total quantity of all orders. * "we need total integrated orders (without quantity loaded)" => what to do you mean? * "In the column Order quantity for next days" => system show a proper quantity based on value typed (number of days)2."We notice that in column blocked system is adding reservation\', \'Comment 10: is wrong too\', \'Comment 11: reservation needs to be removed from Total ordered quantity and Order quantity for next days when VT is loaded. Could you fix this columns too?"* "We notice that in column blocked system is adding reservation" => yes. this quantity is on the truck\', \'Comment 12: but VT is not closed. This quantity is reserved. If we will exclude Reserved quantity from this column (Blocked)\', \'Comment 13: do you need to have a new column e.g. \\\\\\\'Reserved quantity\\\\\\\' ? * "reservation needs to be removed from Total ordered quantity and Order quantity for next days when" => I don\\\\\\\'t understand. If quantity is reserved (VT is not closed) you want to remote it from these 2 columns? But in these 2 columns system shows quantity based on Order. But reservation is related to documents from DHP\', "Comment 14: not from ERP. !44! !75! !105! !Items summary_fields! \'", "Comment 15: \'[[email protected]] przesuniecie status ? Niech teraz klient odpowie.\'", "Comment 16: \'Dear Marcin,What we need and the problems that we have:Current columns in DHP 3.0:1 - Stock: 1.1 Current functionality: is showing total quantity 1.2 Correct functionality: show the total quantity of productions closed (is showing production with pallet label confirmed)2 - Blocked: 2.1 Current functionality: is showing blocked items and with reservation 2.2 Correct functionality: show only blocked items (by warehouse and quality", \'Comment 17: for production and sales) Suggestion: add new column with reservation\', \'Comment 18: and in orders is not change nothing3 - Real available: 2.1 Current functionality: is correct 2.2 Correct functionality:4 - Total Ordered quantity: 2.1 Current functionality: is showing all sales order 2.2 Correct functionality: needs to show total orders less reservation of items loaded Suggestion: add new column with reservation\', \'Comment 19: and in orders is not change nothing5 - Free quantity: 2.1 Current functionality: is correct 2.2 Correct functionality:6 - Ordered quantity for the next days: 2.1 Current functionality: is showing all orders per period 2.2 Correct functionality: show all orders per period less reservation of items loaded Suggestion: add new column with reservation\', \'Comment 20: and in orders is not change nothing7 - Production order in progress: 2.1 Current functionality: is showing all productions with Production order or PLR opened 2.2 Correct functionality: the functionality is correct if the Stock column will be fixed and not show confirmed barcodes. Because in this column is showing production opened and in stock we already have confirmed barcodes\', \'Comment 21: and is duplicationg information. Stock or Production order column should be fixed. If is not possible fix Stock\', \'Comment 22: this column should show only production with barcodes to be confirmed8 - Available stock: 2.1 Current functionality: is correct 2.2 Correct functionality: if create new column with reservation\', \'Comment 23: needs to include in calculationMarcin questions:"we need total integrated orders (without quantity loaded)" => what to do you mean? In DHP 2.5\', \'Comment 24: system add all sales orders/internal orders\', \'Comment 25: and reduce quantity loaded in VT\', "Comment 26: this is what we call of quantity to loaddo you need to have a new column e.g. \\\\\'Reserved quantity\\\\\' ? we had this reservation in previus question", \'Comment 27: the calculation was in total order and order for next days\', \'Comment 28: but yes\', "Comment 29: can be new column.\'", \'Comment 30: "Hi [[email protected]]1 - Stock:1.1 Current functionality: is showing total quantity1.2 Correct functionality: show the total quantity of productions closed (is showing production with pallet label confirmed) [MK]=> so in column we should show all UL\\\'s with status OnStock from WO(IP) for which we have PLR NOT confirmed yet. And these UL\\\'s cannot be shown in colulmn \\\'Production order in progress\\\' ?2 - Blocked:2.1 Current functionality: is showing blocked items and with reservation2.2 Correct functionality: show only blocked items (by warehouse and quality\', \'Comment 31: for production and sales)Suggestion: add new column with reservation\', \'Comment 32: and in orders is not change nothing[MK] => we should add new column Reserved ? and this reserved quantity should be included in column \\\'Real available\\\' or \\\'Available\\\'?"\', "Comment 33: \'[[email protected]] czy możecie przesunąć status taska? Czekamy aktualnie na odpowiedź klienta. Dzięki\'", \'Comment 34: "Hi Marcin1 - Stock:1.1 Current functionality: is showing total quantity1.2 Correct functionality: show the total quantity of productions closed (is showing production with pallet label confirmed)[MK]=> so in column we should show all UL\\\'s with status OnStock from WO(IP) for which we have PLR NOT confirmed yet.And these UL\\\'s cannot be shown in colulmn \\\'Production order in progress\\\' ?[PS] We need to have only one column with PLR in progress. We can\\\'t have productions not finished in column Stock. So column Stock shows only productions confirmed and column Production order in progress show Production order not started and PLR not confirmed.2 - Blocked:2.1 Current functionality: is showing blocked items and with reservation2.2 Correct functionality: show only blocked items (by warehouse and quality\', \'Comment 35: for production and sales)*Suggestion: add new column with reservation\', "Comment 36: and in orders is not change nothing[MK] => we should add new column Reserved ? and this reserved quantity should be included in column \'Real available\' or \'Available\'?[PS] yes", \'Comment 37: you need to add column Reserved. The column should be calculated in the Real available!items!"\', "Comment 38: \'Ordered quantity for next days - rozmawiałem z Priscyla", "Comment 39: w DHP2.5 tutaj liczył również ilości z Orderów dla których data realizacja już jest w przeszłości 0 klient jeszcze nie odebrał\'", "Comment 40: \'[[email protected]]", \'Comment 41: I have discussed with [[email protected]] about these changes in the report and after verification we agreed that it is not a bug\', \'Comment 42: but changes in the report. Please create GDC for this report. We will continue in new GDC.Remark: I think\', "Comment 43: GDC-859 should be delivered after this new GDC will be finished.\'", "Comment 44: \'Dear [[email protected]]Have you raised a GDC task? Can we close this task?Regards\'", \'Comment 45: "Marcin and Aleksandra,I\\\'m asking the same information from report available in DHP 2.5 and 2.7. In GDC-859 we asked improvement (add more columns) but in report we asked the same that was available in old version. I disagree\', \'Comment 46: is not GDC. Can we talk about it?Thank you"]\']\nRelated Issues:\n[]\n\n### End'}
384	{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8648\n\n### Instruction:\nHello, this morning DHP is updated. User now reports that packing slips are not printed for dispatches. Please check and fix as soon as possible. Also pleasse check relation with release to avoid it coming days with other updates\r\n\r\nthanks\n\n### Response:\n["Comment 1: [\'VT-614 and VT-628 are examples\'", "Comment 2: \'Both automatic as manually", "Comment 3: there is no xml send to transform\'", "Comment 4: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", "Comment 5: \'po restarcie usługi printserver poszło.Wcześniej błędy:2023-02-28 14:10:41 (/Plant.Printout.Print.Server/DHVD01AP179/12756/31) [Error] Kotrak.Common.Infrastructure.Integration.Filters.InboundMessagesProcessFilter - Error during process inbound message\'", "Comment 6: \'plugin w config byl zly - poprawa dev.\'", "Comment 7: \'Please check should be working now.\'", "Comment 8: \'You can close the ticket\']"]\nRelated Issues:\n[]\n\n### End'}
385	{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8647\n\n### Instruction:\nUser is working from home and again he has problems with the screen for accounting.\r\nSometimes it goes wel and sometimes it goes wrong.\r\n\r\nSee also DGS-8637\r\n\r\n\n\n### Response:\n["Comment 1: [\'!image-2!!image-3!\'", "Comment 2: \'SDNL-39660\'", "Comment 3: \'!image-4!\'", "Comment 4: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", "Comment 5: \'XL/974177\'", "Comment 6: \'Dear Bert,I have few questions as all your tasks with integrated login and not working Accounting refers to one - the same user.So: 1. Does the issue only appears when user orks from home?2. If yes", \'Comment 7: is user connected via VPN to domain?3. Does other modules behave the same way as Accounting? (if you do not know\', "Comment 8: please ask user to check)4. Does user connect to Terminal Server or he has ERP XL installed on his desktop?Regards\'", "Comment 9: \'When first opening sales and orders and afther this accounting there is no problem.Very strange!image!\'", "Comment 10: \'1. Does the issue only appears when user orks from home?2. If yes", "Comment 11: is user connected via VPN to domain?3. Does user connect to Terminal Server or he has ERP XL installed on his desktop?\'", "Comment 12: \'It appears when he is working from home and on the office connected with kabel\'", "Comment 13: \'2. Is user connected via VPN to domain when working from home?3. Does user connect to Terminal Server or he has ERP XL installed on his desktop?\'", "Comment 14: \'User is always logging in using : Citrix\'", "Comment 15: \'Hello,I have consulted this issue with producer. They suggested one more thing to check. Please", \'Comment 16: see their comment below:_{color:#0747a6}Problems with loading menus may rather be caused by cooperation with printers in the system.{color}__{color:#0747a6}Please verify how the login works if we set the default printer in Windows in the terminal session to the printer from the terminal server named: Microsoft Print to PDF and disable printer mapping when logging into the session.{color}_{color:#172b4d}Please\', "Comment 17: check and let me know.{color}{color:#172b4d}Regards{color}\'", "Comment 18: \'I just reported : User is always logging in using : CitrixHow is it possible that sometimes things go well and sometimes not well?\'", "Comment 19: \'Have you checked printers?\'", "Comment 20: \'To day user can log in the system.There has nothing been changed.Conclusion : When it is an printer issue problem would be always be present. Other users in Citrix do not have any problem.There has also been problems with the response. Service BusinessPlatform had to be stopped and restarted after which the response was good again. This problem is more common.!image-1!\'", "Comment 21: \'!image-2023-03-07-12-23-36-693.png!!image-2023-03-07-12-25-05-141.png!\'", \'Comment 22: "When you restart Business Platform\', "Comment 23: you restartErpintegrator and user\'s session is uploaded. That\'s all{color:#0747a6}_Conclusion : When it is an printer issue problem would be always be present. Other users in Citrix do not have any problem._{color}{color:#172b4d}Conclusion 2: This is not XL issue as other users also login via Citrix and do not have the same issue.{color}{color:#172b4d}Things to check:{color}{color:#172b4d}>> if user is in correct group", \'Comment 24: in cmd or power shell please run on user\\\'s computer:whoami /groups{color}{color:#172b4d}>> please check if this SID agrees with the SID you will find by command:{color}{color:#172b4d}wmic useraccount get name,sid - when you want to verify all users in domain{color}{color:#172b4d}whoami / user - run on user\\\'s computer to check SID !image-2023-03-07-12-30-22-075.png! >> You may also verified if user has relevant hasp key in here: !image-2023-03-07-12-31-18-271.png!{color}{color:#172b4d}Regards{color}"\', "Comment 25: \'!image-5!\'", \'Comment 26: "When you restart Business Platform\', \'Comment 27: you restart Erpintegrator and user\\\'s session is uploaded. That\\\'s all This is needed when we have an very low responce. It cost a lot of time to book just one order. afther restart resounce is oke. This is an comman problem."\', \'Comment 28: "Regarding user NWIJ\', \'Comment 29: please check Bartłomiej\\\'s comment in task related underDGS-8620"\', "Comment 30: \'!image-6!\'", "Comment 31: \'Did You try this solution?!image-2023-03-28-12-17-06-069.png!\'", "Comment 32: \'Conclusion: Every time we add an new user we do have to synchronise account of ERP operators\'", "Comment 33: \'Yes", "Comment 34: ERPXL has only information on user that has been synchronized. It do not have /do not use direct access to Active Directory data.\'", "Comment 35: \'Please", "Comment 36: let me know if expect any additional actions from us regarding this issue? Can we close this ticket?\'", "Comment 37: \'Ticket can be closed\']"]\nRelated Issues:\n[\'DGS-8620\']\n\n### End'}
386	{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8646\n\n### Instruction:\nwe have problem with item SUN0895-T-S30, WO(OB)-22/2/23, 89-OB35N, is with reservation but we cancelled the dispatch and quantity didn\'t back.\r\n\r\nCould you check why the stock didn\'t back?\r\n\r\nWe need to load\r\n\r\n\n\n### Response:\n["Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", "Comment 2: \'Hi [[email protected]],As [[email protected]]mentioned in the incident DGS-8640,we verified this option to cancel element and in our examples it worked. Could you please describe step by step how did you make this cancellation please?Regards\'", "Comment 3: \'Hi,Any feedback?Regards\'", "Comment 4: \'Hi Aleksandra[[email protected]] will please provide a feedback for it asap.Thank you very much\'", "Comment 5: \'I think it could be the same example as DGS-8715\'", "Comment 6: \'Hi [[email protected]]", \'Comment 7: [[email protected]],This is the same issue as under RCA DGS-8715 and solved inGDC-849.Please\', "Comment 8: confirm if we can close this task.Regards\'", "Comment 9: \'Hi [[email protected]]You can close this task.Thank you very much\'", "Comment 10: \'Thank you.Regards\']"]\nRelated Issues:\n[\'DGS-8640\', \'DGS-8715\']\n\n### End'}
387	{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8645\n\n### Instruction:\nMany no license error messages in VT \r\n\n\n### Response:\n["Comment 1: [\'!image!!image-1!!image-2!\'", "Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", "Comment 3: \' !screenshot-1! !image-2023-03-01-09-14-44-098!vt-1010/2vt-1014/2vt-402/1!image-2023-03-01-09-22-46-232!\'", \'Comment 4: "Hi\', \'Comment 5: there was a communication problem with the XL api - currently the documents are generated.In addition I corrected the data in XL for related orders in VT\\\'s:vt-1010/2,vt-1014/2,vt-402/1."\', "Comment 6: \'Problen seems to be soveld.!image-3!\'", "Comment 7: \'Ticket may be closed\'", "Comment 8: \'Thank you for confirmation.\']"]\nRelated Issues:\n[]\n\n### End'}
388	{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8644\n\n### Instruction:\nHi\r\n\r\nBoth weighbridges from Rio Claro (089) and Unit2 (090) had stop the continuous communication with DHP 3.0 since Thursday.\r\nSometimes is displays the value, sometimes not.\r\nWe checked with weighbridge supplier and there are no technical issue with weighbridges.\r\n\r\nCould you check it please?\r\n\r\nThank you very much\n\n### Response:\n["Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", "Comment 2: \'Hello,It should be fine now", "Comment 3: The problem has been resolved?Regards\'", \'Comment 4: "Hi AdrianI\\\'ve just got the confirmation from weighbridge operators and now the weighbridge communication is stable.You can close this taskThank you very much!"\', "Comment 5: \'(y)\'", "Comment 6: \'[[email protected]] tu już możesz zmienić status", "Comment 7: chyba nie jest potrzeby przesuwać do [[email protected]] ?\']"]\nRelated Issues:\n[]\n\n### End'}
389	{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8643\n\n### Instruction:\nSince yesterday 27/02/2023 The production have done some production order and we cannot see them in PCS to start the production. Please can you help\n\n### Response:\n["Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", "Comment 2: \'Hi,I have restarted application pools. Now I can see integration started working.Please", "Comment 3: check on your side and confirm.Regards\'", \'Comment 4: "Hi ALeksandra\', \'Comment 5: it\\\'s fine we can see the production order now. ThanksRegards"\', "Comment 6: \'Thank you\'", "Comment 7: \'{code:java}2023-02-27 09:44:34 (/Plant.PCS.BusinessLogic/CIAPP04/2480/1) [Error] Plant.PCS.BusinessLogic.Infrastructure.Startup - An error occurred while seeding the database.Microsoft.Data.SqlClient.SqlException (0x80131904): A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider", \'Comment 8: error: 40 - Could not open a connection to SQL Server) ---> System.ComponentModel.Win32Exception (53): The network path was not found. at Microsoft.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception\', \'Comment 9: Boolean breakConnection\', \'Comment 10: Action`1 wrapCloseInAction) at Microsoft.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj\', \'Comment 11: Boolean callerHasConnectionLock\', \'Comment 12: Boolean asyncClose) at Microsoft.Data.SqlClient.TdsParser.Connect(ServerInfo serverInfo\', \'Comment 13: SqlInternalConnectionTds connHandler\', \'Comment 14: Boolean ignoreSniOpenTimeout\', \'Comment 15: Int64 timerExpire\', \'Comment 16: Boolean encrypt\', \'Comment 17: Boolean trustServerCert\', \'Comment 18: Boolean integratedSecurity\', \'Comment 19: Boolean withFailover\', \'Comment 20: SqlAuthenticationMethod authType) at Microsoft.Data.SqlClient.SqlInternalConnectionTds.AttemptOneLogin(ServerInfo serverInfo\', \'Comment 21: String newPassword\', \'Comment 22: SecureString newSecurePassword\', \'Comment 23: Boolean ignoreSniOpenTimeout\', \'Comment 24: TimeoutTimer timeout\', \'Comment 25: Boolean withFailover) at Microsoft.Data.SqlClient.SqlInternalConnectionTds.LoginNoFailover(ServerInfo serverInfo\', \'Comment 26: String newPassword\', \'Comment 27: SecureString newSecurePassword\', \'Comment 28: Boolean redirectedUserInstance\', \'Comment 29: SqlConnectionString connectionOptions\', \'Comment 30: SqlCredential credential\', \'Comment 31: TimeoutTimer timeout) at Microsoft.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(TimeoutTimer timeout\', \'Comment 32: SqlConnectionString connectionOptions\', \'Comment 33: SqlCredential credential\', \'Comment 34: String newPassword\', \'Comment 35: SecureString newSecurePassword\', \'Comment 36: Boolean redirectedUserInstance) at Microsoft.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity\', \'Comment 37: SqlConnectionString connectionOptions\', \'Comment 38: SqlCredential credential\', \'Comment 39: Object providerInfo\', \'Comment 40: String newPassword\', \'Comment 41: SecureString newSecurePassword\', \'Comment 42: Boolean redirectedUserInstance\', \'Comment 43: SqlConnectionString userConnectionOptions\', \'Comment 44: SessionData reconnectSessionData\', \'Comment 45: Boolean applyTransientFaultHandling\', \'Comment 46: String accessToken\', \'Comment 47: DbConnectionPool pool) at Microsoft.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options\', \'Comment 48: DbConnectionPoolKey poolKey\', \'Comment 49: Object poolGroupProviderInfo\', \'Comment 50: DbConnectionPool pool\', \'Comment 51: DbConnection owningConnection\', \'Comment 52: DbConnectionOptions userOptions) at Microsoft.Data.ProviderBase.DbConnectionFactory.CreatePooledConnection(DbConnectionPool pool\', \'Comment 53: DbConnection owningObject\', \'Comment 54: DbConnectionOptions options\', \'Comment 55: DbConnectionPoolKey poolKey\', \'Comment 56: DbConnectionOptions userOptions) at Microsoft.Data.ProviderBase.DbConnectionPool.CreateObject(DbConnection owningObject\', \'Comment 57: DbConnectionOptions userOptions\', \'Comment 58: DbConnectionInternal oldConnection) at Microsoft.Data.ProviderBase.DbConnectionPool.UserCreateRequest(DbConnection owningObject\', \'Comment 59: DbConnectionOptions userOptions\', \'Comment 60: DbConnectionInternal oldConnection) at Microsoft.Data.ProviderBase.DbConnectionPool.TryGetConnection(DbConnection owningObject\', \'Comment 61: UInt32 waitForMultipleObjectsTimeout\', \'Comment 62: Boolean allowCreate\', \'Comment 63: Boolean onlyOneCheckConnection\', \'Comment 64: DbConnectionOptions userOptions\', \'Comment 65: DbConnectionInternal& connection) at Microsoft.Data.ProviderBase.DbConnectionPool.TryGetConnection(DbConnection owningObject\', \'Comment 66: TaskCompletionSource`1 retry\', \'Comment 67: DbConnectionOptions userOptions\', \'Comment 68: DbConnectionInternal& connection) at Microsoft.Data.ProviderBase.DbConnectionFactory.TryGetConnection(DbConnection owningConnection\', \'Comment 69: TaskCompletionSource`1 retry\', \'Comment 70: DbConnectionOptions userOptions\', \'Comment 71: DbConnectionInternal oldConnection\', \'Comment 72: DbConnectionInternal& connection) at Microsoft.Data.ProviderBase.DbConnectionInternal.TryOpenConnectionInternal(DbConnection outerConnection\', \'Comment 73: DbConnectionFactory connectionFactory\', \'Comment 74: TaskCompletionSource`1 retry\', \'Comment 75: DbConnectionOptions userOptions) at Microsoft.Data.SqlClient.SqlConnection.TryOpen(TaskCompletionSource`1 retry\', \'Comment 76: SqlConnectionOverrides overrides) at Microsoft.Data.SqlClient.SqlConnection.Open(SqlConnectionOverrides overrides) at Microsoft.EntityFrameworkCore.Storage.RelationalConnection.OpenInternal(Boolean errorsExpected) at Microsoft.EntityFrameworkCore.Storage.RelationalConnection.Open(Boolean errorsExpected) at Microsoft.EntityFrameworkCore.SqlServer.Storage.Internal.SqlServerDatabaseCreator.<>c__DisplayClass18_0.<Exists>b__0(DateTime giveUp) at Microsoft.EntityFrameworkCore.ExecutionStrategyExtensions.<>c__DisplayClass12_0`2.<Execute>b__0(DbContext c\', \'Comment 77: TState s) at Microsoft.EntityFrameworkCore.SqlServer.Storage.Internal.SqlServerExecutionStrategy.Execute[TState,TResult](TState state\', \'Comment 78: Func`3 operation\', \'Comment 79: Func`3 verifySucceeded) at Microsoft.EntityFrameworkCore.ExecutionStrategyExtensions.Execute[TState,TResult](IExecutionStrategy strategy\', \'Comment 80: TState state\', \'Comment 81: Func`2 operation\', "Comment 82: Func`2 verifySucceeded) at Microsoft.EntityFrameworkCore.SqlServer.Storage.Internal.SqlServerDatabaseCreator.Exists(Boolean retryOnNotExists) at Microsoft.EntityFrameworkCore.SqlServer.Storage.Internal.SqlServerDatabaseCreator.Exists() at Microsoft.EntityFrameworkCore.Migrations.HistoryRepository.Exists() at Microsoft.EntityFrameworkCore.Migrations.Internal.Migrator.Migrate(String targetMigration) at Microsoft.EntityFrameworkCore.RelationalDatabaseFacadeExtensions.Migrate(DatabaseFacade databaseFacade) at Plant.PCS.BusinessLogic.Infrastructure.EF.BaseDbInitializer`1.Init() in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\9ecc36be9059f942\\\\\\\\Plant.PCS.BusinessLogic\\\\\\\\Infrastructure.EF\\\\\\\\BaseDbInitializer.cs:line 11 at Plant.PCS.BusinessLogic.Infrastructure.SeedingExtension.SeedDatabase(IApplicationBuilder builder) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\9ecc36be9059f942\\\\\\\\Plant.PCS.BusinessLogic\\\\\\\\Infrastructure\\\\\\\\SeedingExtension.cs:line 19ClientConnectionId:00000000-0000-0000-0000-000000000000Error Number:53,State:0,Class:20{code}\'", \'Comment 83: "{code:java}2023-02-27 09:44:41 (/Plant.PCS.BusinessLogic/CIAPP04/2480/10) [Error] Kotrak.Integration.InternalStorage.IInternalStorageRepository - Error during System.Collections.Generic.IReadOnlyCollection`1[Kotrak.Integration.InternalStorage.EF.Entities.OutboundEntity] Get(Int32) methodSystem.ObjectDisposedException: Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling \\\'Dispose\\\' on the context instance\', \'Comment 84: or wrapping it in a using statement. If you are using dependency injection\', "Comment 85: you should let the dependency injection container take care of disposing context instances.Object name: \'IntercontextCommunicationDbContext\'. at Microsoft.EntityFrameworkCore.DbContext.CheckDisposed() at Microsoft.EntityFrameworkCore.DbContext.get_ContextServices() at Microsoft.EntityFrameworkCore.DbContext.get_ChangeTracker() at Microsoft.EntityFrameworkCore.Query.CompiledQueryCacheKeyGenerator.GenerateCacheKeyCore(Expression query", \'Comment 86: Boolean async) at Microsoft.EntityFrameworkCore.Query.RelationalCompiledQueryCacheKeyGenerator.GenerateCacheKeyCore(Expression query\', \'Comment 87: Boolean async) at Microsoft.EntityFrameworkCore.SqlServer.Query.Internal.SqlServerCompiledQueryCacheKeyGenerator.GenerateCacheKey(Expression query\', \'Comment 88: Boolean async) at Microsoft.EntityFrameworkCore.Query.Internal.QueryCompiler.Execute[TResult](Expression query) at Microsoft.EntityFrameworkCore.Query.Internal.EntityQueryable`1.GetEnumerator() at System.Collections.Generic.List`1..ctor(IEnumerable`1 collection) at System.Linq.Enumerable.ToList[TSource](IEnumerable`1 source) at Castle.Proxies.Invocations.IInternalStorageRepository`1_Get_2.InvokeMethodOnTarget() at Castle.DynamicProxy.AbstractInvocation.Proceed() at Kotrak.Common.Infrastructure.Interceptors.LoggingInterceptor`1.Intercept(IInvocation invocation){code}"\', "Comment 89: \'[PCS - sprawdzenie co przeszło PLR", \'Comment 90: sprawdzenie\', "Comment 91: co powoduje error\|onenote:https://kotrak.sharepoint.com/sites/erpasysta/Shared%20Documents/Baza%20wiedzy/Baza%20Wiedzy%20-%20ERPSD/Klienci/DEHEUS/DEHEUS%20APPLICATIONS/Egipt/Baza%20wiedzy.one#PCS%20-%20sprawdzenie%20co%20przesz%C5%82o%20PLR,%20sprawdzenie,%20co%20powoduje%20error&section-id=\\\\\\\\{145A51F6-5D2A-42D7-9D47-CB2FD0A15DC7}&page-id=\\\\\\\\{CB544F8A-92FA-47BF-BBB7-5ECB11257E4E}&end] ([Widok sieci Web\|https://kotrak.sharepoint.com/sites/erpasysta/_layouts/OneNote.aspx?id=%2Fsites%2Ferpasysta%2FShared%20Documents%2FBaza%20wiedzy%2FBaza%20Wiedzy%20-%20ERPSD&wd=target%28Klienci%2FDEHEUS%2FDEHEUS%20APPLICATIONS%2FEgipt%2FBaza%20wiedzy.one%7C145A51F6-5D2A-42D7-9D47-CB2FD0A15DC7%2FPCS%20-%20sprawdzenie%20co%20przesz%C5%82o%20PLR%2C%20sprawdzenie%2C%20co%20powoduje%20error%7CCB544F8A-92FA-47BF-BBB7-5ECB11257E4E%2F%29])\']"]\nRelated Issues:\n[]\n\n### End'}
390	{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8642\n\n### Instruction:\nGood morning,\r\n\r\nCan you please approve me to see all the incidents and requests created by anyone in Serbia? I have already asked for this (DGS-8533) and for the time being I had rights but now again I dont. For example I can not see DGS-8633 which is created by Nemanja Antonic and it is crucial but I can not see it. Check the screenshot. I should have all the rights just like Nemanja Antonic. Thank you.\n\n### Response:\n["Comment 1: [\'!image-1!\'", "Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", "Comment 3: \'Dear Miroslav", \'Comment 4: In reference to your request I added You to all open Incidents. Additionally\', \'Comment 5: I added You to the request participants sections\', "Comment 6: all new tickets from Serbia will be visible to You.\'", "Comment 7: \'It is OK now", "Comment 8: thank you !\']"]\nRelated Issues:\n[]\n\n### End'}
391	{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8641\n\n### Instruction:\n# On new Financial Statement printouts should be section Guarantees when there will be some invoices with Round Category = \'Guarantees\'.\r\nThis section should be displayed only when will be some invoices with this Round Category for the round, when there is no data in this section it shoudln\'t appear on printout.\r\n\r\n\r\n # Guarantees should be also included in Feed profit\xa0(it is an extra revenue) - to change technical results calculating procedure\r\n\r\n!image-2023-02-28-08-58-04-195.png!\r\n\r\n\xa0\n\n### Response:\n["Comment 1: [\'[[email protected]]can you specify how should looks section of guarantees on printout.What columns should be on printout for this section", "Comment 2: on old printout it looks like that!image-2023-02-28-09-11-58-171.png!How should be calculated guarantees for feed profit. It should be always added to the Feed profit values?Should we take always absolute values (when it be positive or negative values of guarantees)?\'", \'Comment 3: \\\'I can be almost the same columns as for the category "Opzetgegevens" above it:Datum (date)\', \'Comment 4: referentie (reference)\', \'Comment 5: aantal (quantity)\', \'Comment 6: gewicht (weight)\', "Comment 7: prijs excl. VAT (price) and bedrag excl. BTW (net value)Guarantees can be positive or negative. When it is negative in the Financial Statement than it is a revenu (just like SLAC). In this case you can print it as positive on the PFD and add this amount to the feed profit.When it is positive in the Financial Statement you must print it as negative on the PDF and extract this from the feed profit (voerwinst). \'", "Comment 8: \'[[email protected]]do zweryfikowania czy przeniesione i gotowe do testu/na prod.\'", "Comment 9: \'I made a positive guarantee invoice (3763,00 EUR)", \'Comment 10: but it shows on the printout as negative (like the old printouts). 1. I know if this was the plan\', \'Comment 11: because on the new FS also the meat price amounts are positive? 2. For the calculations\', \'Comment 12: does it add up\', \'Comment 13: for the calculations down below? Because I would expect "marge/m²" (revenue/m²) to be 8.50 in stead of 7.79 when I add the guarantee amount to the rest. !image!\\\'\', \'Comment 14: "The guarantees amount isn\\\'t included in the feed profit (marge). Therefor\', \'Comment 15: the revenue/m² (marge/m²) is wrong."\', "Comment 16: \'Please see mu note from March 1:Guarantees can be positive or negative. When it is negative in the Financial Statement than it is a revenu (just like SLAC). In this case you can print it as positive on the PFD and add this amount to the feed profit.When it is positive in the Financial Statement you must print it as negative on the PDF and extract this from the feed profit (voerwinst).\'", "Comment 17: \'Yes", "Comment 18: your explanation is correct Mitch. Could this be modified asap?\'", "Comment 19: \'Dla nowych wydruków FS pokazujemy faktyczną jej wartość z faktury (inaczej niż na dokumencie FS", "Comment 20: gdzie pokzywana jest wartość mnożona przez -1). Stare wydruki FS zostają niezmienione (tam pokazywana jest wartość taka jak na dokumencie FS).Do kalkulacji Feed profit powinna być wliczana oryginalna wartość z faktur i powinno to wyglądać tak: (ABS(@AmountFL)+ABS(@AmountAL)) - ABS(@AmountOfFeed) -ABS(@AmountDOCNet) +Suma faktur gwarancyjnych\'", \'Comment 21: "[[email protected]],we\\\'ve made changes for Guarantees and Feed Profit calculation in test Intense environment. You can verify it.Best regards,Grzegorz"\', "Comment 22: \'Hello Grzegorz,Something still seems off to me in the caclulations.When I do the manual calculation for this example I do:Feed profit = Slaughtery + Guarantee - Feed - Broilers--> 238.375,80 + 9.882,39 - 172.091,44 - 31.141,80 = 45.024,95 EURThe printout however shows 45.617,89 EURThis is a difference of 592,94 EURCould you see where this difference comes from?I took another example and there the difference was even bigger.!Example technical result calculation error.JPG\|thumbnail!\'", "Comment 23: \'Hello [[email protected]],we took the wrong value for guarantees - gross value. We adjusted it for net value. You can feel free to test the calulcation one more time.Best regards,Grzegorz\'", "Comment 24: \'Hello Grzegorz,I tested it and now it seems to be right indeed.You may move this to PROD", "Comment 25: thank you!\'", "Comment 26: \'[[email protected]],we moved calulcation for Feed Profit into prod Intense environment. You can verify it.Best regards,Grzegorz\'", \'Comment 27: \\\'Grzegorz,This is good now in PROD environment. I think you can close this.The last modifications on FS new and S2P will be handled in the other JIRA task I suppose?https://helpdesk.kotrak.com/servicedesk/customer/portal/56/DGS-8067"2. On FS new\', \'Comment 28: the entry stock and final stock are still in Dutch on French printouts""One more question\', \'Comment 29: for feed lines we have "voer\\\\\\\' as description on the S2P and for one sided SI\\\\\\\'s where the customer is both the supplier and the reference\', \'Comment 30: we have "Salmonellafonds" as description on the S2P. Could these fields be translated as well\', \'Comment 31: looking to the customer card for the correct translation?"\\\'\', "Comment 32: \'I close this task.Yes", "Comment 33: translations will be handled in this task.https://helpdesk.kotrak.com/servicedesk/customer/portal/56/DGS-8067\']"]\nRelated Issues:\n[\'DGS-8215\', \'DGS-8732\', \'DGS-8877\']\n\n### End'}
392	{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8640\n\n### Instruction:\nwe have problem with item SUN0895-T-S30, WO(OB)-22/2/23, 89-OB35N, is with reservation but we cancelled the dispatch and quantity didn\'t back.\r\n\r\nCould you check why the stock didn\'t back?\r\n\r\nWe need to load\r\n\r\n\n\n### Response:\n["Comment 1: [\'!image!\'", "Comment 2: \'Hello", "Comment 3: We kindly inform you that wecurrentlyare processing another Priority1 task.We will revert to processing your task as soon as possible.Regards\'", "Comment 4: \'Hello,Stock came back.In this task we have focused on clearingandunblocking the process.If there is a need from your sideto investigate the reasonof the issue", \'Comment 5: we may raise RootCause Analysis (RCA)task for you.Please\', "Comment 6: let us knowhow you wish us to proceed.Regards\'", "Comment 7: \'Hello Aleksandra,yes", "Comment 8: we need RCA. You can close this task. Thank you.\'", "Comment 9: \'The RCA task is underDGS-8646.Please", "Comment 10: let us know if you have access.Regards\'", "Comment 11: \'Dear [[email protected]]we verified this option to cancel element and in our examples it worked. Could you please describe step by step how did you make this cancellation please?\'", \'Comment 12: "Marcin,we didn\\\'t cancel the element\', \'Comment 13: we cancelled the WD using option clear element.!image-1!"]\']\nRelated Issues:\n[\'DGS-8646\', \'DGS-8715\']\n\n### End'}
393	{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8639\n\n### Instruction:\nthe prouction 0871240223014 is closed on DHP but is not available in DHC. Could you check why? We need to invoice but it\'s not possible without integration.\r\n\r\n\n\n### Response:\n["Comment 1: [\'!image!\'", "Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", "Comment 3: \'id=1add05fd-f979-4c0c-80ad-427939754cc5!image-2023-02-27-20-44-11-521.png!\'", \'Comment 4: "{code:java}2023-02-24 12:49:41 (2e8b0cd0-a4dd-4846-951b-1bd01b4935a5/Plant.DHC.Integration/BR-4-SV-VM0204/18912/8) [Error] Plant.Integration.DhcService.Application.DhpToDhcMapFilter - Couldn\\\'t map dhp message Plant.QAM.BusinessLogic.DomainAbstractions.Quarantine.ProductionLotReportQuarantineSynchronizationEventKotrak.Integration.IdentityMapping.IdentityNotMappedException: Key of entity ProductionLotReportIdentityEntity was not mapped. Key value Id: 1add05fd-f979-4c0c-80ad-427939754cc5 at Kotrak.Integration.IdentityMapping.EF.GenericIdentityMappingRepository`1.GetExternalKey(GuidKey key) at Plant.Integration.DhcService.Application.ProductionLotReports.ProductionLotReportQuarantineMapFilter.MapIds(ProductionLotReportQuarantineSynchronizationEvent message\', \'Comment 5: ProductionLotReportQuarantine externalObject) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\e810c04f78ab209c\\\\\\\\Plant.Integration.DhcService\\\\\\\\Plant.Integration.DhcService.Application\\\\\\\\ProductionLotReports\\\\\\\\ProductionLotReportQuarantineMapFilter.cs:line 28 at Plant.Integration.DhcService.Application.DhpToDhcMapFilter`2.Process(PackageIntegrationState input) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\e810c04f78ab209c\\\\\\\\Plant.Integration.DhcService\\\\\\\\Plant.Integration.DhcService.Application\\\\\\\\DhpToDhcMapFilter.cs:line 44{code}"\', "Comment 6: \'!image-2023-02-27-21-10-10-961.png!!image-2023-02-27-21-13-01-804.png!\'", "Comment 7: \'Hi,The issue was caused that PLR used Recipe ver 14 which was not in DHC. I have resynced recipe from DHH", \'Comment 8: it appeared in DHC. Now we need to resend PLR but it needs to be moved back to status finished and then again confirmed. But when we confirm it fromapplication\', \'Comment 9: we receive error:Current settlement configuration requires that deliveries are explicitly specified appears". So we need to change configuration for a moment. Do you agree for that?Regards\\\'\', "Comment 10: \'Co jest niepokojące", \'Comment 11: w tabeli eventów dla Prod jest ponad 6800 eventów\', "Comment 12: z czego 6652 wywołane przez PCSa!image-2023-02-28-07-45-46-813.png!!image-2023-02-28-07-46-14-311.png!\'", \'Comment 13: \\\'Po wysłaniu messega z dhp{code:java}2023-02-27 17:17:36 (2e8b0cd0-a4dd-4846-951b-1bd01b4935a5/Plant.DHC.Integration/BR-4-SV-VM0204/15496/8) [Error] Kotrak.Integration.IntegrationPluginCommon.IntercontextCommunication.Inbound.InboundIntercontextErrorHandler - Error during handling message of type "Plant.QAM.BusinessLogic.DomainAbstractions.Quarantine.ProductionLotReportQuarantineSynchronizationEvent"\', \'Comment 14: retry no 2Kotrak.Integration.IdentityMapping.IdentityNotMappedException: Key of entity ProductionLotReportIdentityEntity was not mapped. Key value Id: 1add05fd-f979-4c0c-80ad-427939754cc5 at Kotrak.Integration.IdentityMapping.EF.GenericIdentityMappingRepository`1.GetExternalKey(GuidKey key) at Plant.Integration.DhcService.Application.IdentityMappingExtensions.GetMappedExternalLongKey[TEntity](IIdentityMappingRepository`1 identityMapper\', \'Comment 15: AggregateId id) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\e810c04f78ab209c\\\\\\\\Plant.Integration.DhcService\\\\\\\\Plant.Integration.DhcService.Application\\\\\\\\IdentityMappingExtensions.cs:line 20 at Plant.Integration.DhcService.Application.ProductionLotReports.ProductionLotReportQuarantineMapFilter.MapIds(ProductionLotReportQuarantineSynchronizationEvent message\', \'Comment 16: ProductionLotReportQuarantine externalObject) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\e810c04f78ab209c\\\\\\\\Plant.Integration.DhcService\\\\\\\\Plant.Integration.DhcService.Application\\\\\\\\ProductionLotReports\\\\\\\\ProductionLotReportQuarantineMapFilter.cs:line 26 at Plant.Integration.DhcService.Application.DhpToDhcMapFilter`2.Process(PackageIntegrationState input) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\e810c04f78ab209c\\\\\\\\Plant.Integration.DhcService\\\\\\\\Plant.Integration.DhcService.Application\\\\\\\\DhpToDhcMapFilter.cs:line 44 at Kotrak.Integration.Pipeline.PredefinedFilters.FilterBase`1.Execute(T input) at Kotrak.Integration.Pipeline.Pipeline`1.Excecute(T input) at Plant.Integration.DhcService.Application.BasePushPipelineExecutor`4.RunPipeline(IDhcService dhcService\', "Comment 17: TMessage message) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\e810c04f78ab209c\\\\\\\\Plant.Integration.DhcService\\\\\\\\Plant.Integration.DhcService.Application\\\\\\\\BasePushPipelineExecutor.cs:line 29 at Plant.Integration.DhcService.Infrastructure.Handlers.BaseInboundMessageHandler`1.Handle(TEvent message) in C:\\\\\\\\BuildAgent\\\\\\\\work\\\\\\\\e810c04f78ab209c\\\\\\\\Plant.Integration.DhcService\\\\\\\\Plant.Integration.DhcService.Infrastructure\\\\\\\\Handlers\\\\\\\\BaseInboundMessageHandler.cs:line 37 at Kotrak.Integration.IntegrationPluginCommon.IntercontextCommunication.Inbound.IntercontextInboundHandler`2.Handle(InternalStorageDto message){code}\'", "Comment 18: \'!image-2023-02-28-08-50-49-661.png!\'", "Comment 19: \'Hi [[email protected]],We have discussed this issue with Dev and the quickest option would be to do this PLR report in ERP system manually. Please", "Comment 20: let us know if this would be fine for you.Regards\'", "Comment 21: \'Hi Aleksandra,we need the integration. Why is not possible integrate?\'", "Comment 22: \'Hi,It is another incident", "Comment 23: the sam as in task DGS-8387. For further solution we need to pass this task to Dev Team. We will let you know about the solution as soon as possible.Regards\'", \'Comment 24: "Hi AleksandraAbout changing configuration from Delivery to Mixed or FIFO\', "Comment 25: we do not accept this because this plant has special traceability from MAPA and I\'m afraid of this causing errors in consumption of wrong RM SerialNumber.About manual ajdustment on ERP", \'Comment 26: will take some time\', \'Comment 27: but it\\\'s possible.However we need this PLR integrated to DHC because we have some BI Dashboards that gets data from DHC database.This PLR is important on the process.Thank you very much"\', \'Comment 28: "Hi Maicon,We won\\\'t change configuration as it would cause another use of material. As I mentioned above\', \'Comment 29: I will pass this task to dev team. The issue is rather caused by short response time so we will decrease it. No need for RCA right now.Regards"\', "Comment 30: \'[^production_lot_confirmed_event.txt]\'", "Comment 31: \'Lot Report in DHC now!image-2023-02-28-14-44-04-098.png!Regards\'", "Comment 32: \'Hello Aleksandra,the lot number is available in DHC. You can close this task. Thank you.\']"]\nRelated Issues:\n[]\n\n### End'}
394	{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8638\n\n### Instruction:\nApplication does not respond anymore.\r\n\r\nAll the time : Please wait\r\n\r\nCan not get out of application\n\n### Response:\n["Comment 1: [\'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", "Comment 2: \' !screenshot-1! \'", "Comment 3: \'Please check there was a problem with the processes of the Erpintegrator service - after restarting service the applications should now run properly.\'", "Comment 4: \'Responce is beter. How to restart Erpintegrator service?What is the procedure to do this\'", \'Comment 5: "Hi,this task did not give an error in description or more details to analysis so you can see that yesterday there was a high process load on the service. !screenshot-2! As for restarting start BP !screenshot-4! and go to applications !screenshot-3! select the stop and start option - checking if it started.keep in mind that this won\\\'t always help\', \'Comment 6: so in case of problems it\\\'s best to create a task.Regards."\', "Comment 7: \'Ticket can be closed\']"]\nRelated Issues:\n[]\n\n### End'}
395	{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8637\n\n### Instruction:\nNiels Wijnen has trouble in accounting screen in CDN.\r\n\r\nHe wants to get into Accounting using the button accounting. Then he gets the gray screen according screen shot. Last Thursday when he was in the office Veghel it went well. \r\nHe also can\'t close the gray screen which keeps him logged in and has to ask someone else to kick kim out.\r\n\r\n\r\n\n\n### Response:\n["Comment 1: [\'!image!!image-1!\'", "Comment 2: \'!image-2!\'", "Comment 3: \'Suddenly ", \'Comment 4: afther 5 hours\', "Comment 5: it works again.Ticket can be closed.\'", "Comment 6: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", "Comment 7: \'User has still problem with loging in DH-CDN!image-3!\'", "Comment 8: \'!image-4!\'", "Comment 9: \'I will open a new ticket for DH-CDN inlog problem.\']"]\nRelated Issues:\n[\'DGS-8620\']\n\n### End'}
396	{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8636\n\n### Instruction:\nCan we make the fields Hakdermatitus and the table for Footsole scores changeable even after the SR is archived? \n\n### Response:\n["Comment 1: [\'!image!!image-1!\'", "Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", \'Comment 3: "Unfortunately it\\\'s hard to make possible some fields editable when document is archived. # In this case it\\\'s needed to allow users to modify documents in Archive (any field or table on documents) and give them rights to editing any document - it means that users will be able to edit all documents in Archive (now few users have this right). It could be dangerous if all users will have this rights. To avoid changing other documents by users there will be needed configure all fields on all documents and add edit condition for each of them and then we can set which field/tab will be editable (it could be editable for users in some role) even if document will be in Archive\', \'Comment 4: but it\\\'s a time-consuming solution. # Second option that we discussed internally is to create some action to update only these specific fields/tables for this type of document (in this case SR). We can make some mockup of this to visualize how could it works. It could be something like action from lightning button where we retrive actual data on popup window and user can modify some data and update these values.We can make some mockup of 2nd solution if you prefer this option.Regards"\', \'Comment 5: "Indeed lets look at your proposal for the second option. The first option I don\\\'t want to have."\', "Comment 6: \'It could looks like that in this video [^SR_field_modifying.wmv]", "Comment 7: is it good and can we implement it on test environment?\'", "Comment 8: \'Can be moved to PROD and topic closed.\'", "Comment 9: \'Do dokończenie na test i później do przeniesienia na prod.\'", \'Comment 10: \\\'[[email protected]],we\\\\\\\'ve adjusted and added MS SQL code for update in test environment. You can feel free to test it on Slaughtery Report in the "Archive" status.Best regards,Grzegorz\\\'\', "Comment 11: \'Hi Grzegorz", \'Comment 12: It looks like I can edit all fields on the SR when it has the status Archive. That is not what we want. Regards\', \'Comment 13: Mitch Van: Grzegorz Materla (Jira) <[email protected]> Verzonden: maandag 17 april 2023 13:26 Aan: Bovene\', "Comment 14: Mitch van <[email protected]> Onderwerp: DGS-8636 SR fields available after archive \'", "Comment 15: \'Can we make the fields Hakdermatitus and the table for Footsole scores changeable even after the SR is archived?\'", \'Comment 16: \\\'Hi Mitch,you can edit documents in "Archive" status\', \'Comment 17: because you have all rights on TEST environment.Others users can\\\\\\\'t do it. We made test on Anja Verdam and the SR in "Archive" was not editable.Best regards,Grzegorz\\\'\', "Comment 18: \'Ah", "Comment 19: so that is the reason.It can be moved to PROD whenever that is the case.\']"]\nRelated Issues:\n[\'DGS-8748\']\n\n### End'}
397	{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8635\n\n### Instruction:\nwe create some XML from analysis order for BLGG but the file was not sent to ftp://[email protected]/DHImpData.\r\nI checked folder in internal server and file was create but not sent.\r\n\r\nCould you check if we have some error?\r\n\r\nThank you\n\n### Response:\n["Comment 1: [\'!image!\'", "Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", "Comment 3: \'Hello,You need to configure / share XML folder with FTP server and this is to do on your side. We are not authorised", \'Comment 4: what is more\', \'Comment 5: the password needs to be set up. If you do not know how to do that\', "Comment 6: please contact IT in Netherlands. They are experienced.All new xml files will then drop to ftp. The below files need to be moved manually.Regards!image-2023-02-27-14-11-09-471.png!\'", "Comment 7: \'Hi Aleksandra,we are checking internally. You can close this task. Thank you.\'", "Comment 8: \'Thank you\']"]\nRelated Issues:\n[]\n\n### End'}
398	{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8634\n\n### Instruction:\nan automatic RM assignment is created. however, there are 2 times the same pallet in one order. When the employee scans the pallet, he receives an error message and cannot continue.\r\n\r\nWhen it reboots and starts again the same thing happens again.\r\n\r\n\n\n### Response:\n["Comment 1: [\'!image!!image-1!\'", "Comment 2: \'This is happening more often.!image-2!!image-3!\'", "Comment 3: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", "Comment 4: \'Please be informed that we have forwarded the issue to the development team in order to internal analysis.We are waiting for more details and will be back with further information as soon as possible.\'", "Comment 5: \' !Log WMO 3282! !WMO RM 1895!\'", "Comment 6: \' !WMO RM 659-03-23! !image-2023-03-06-18-36-17-799!!image-2023-03-06-18-40-53-708!\'", "Comment 7: \'What is the status at this moment?\'", "Comment 8: \'Hi,This task is under dev investigation. We will let you know about the result as soon as possible.Regards\'", "Comment 9: \'Comment of user : It strikes me that this always concerns the pallets that are just NOT 500 kg\'", "Comment 10: \'!image-4!\']"]\nRelated Issues:\n[\'DGS-8560\']\n\n### End'}
399	{'prompt': 'Below is a description that describes an issue. Write a response that will help solve the problem.\n\n\n### Issue Key:\nDGS-8633\n\n### Instruction:\nWe need to add this item to stock also. \n\n### Response:\n["Comment 1: [\'!vukota dodavanje 21.02.2023 (1)!\'", "Comment 2: \'Hello,We are investigating your issue. We will inform you about the solution as soon as possible.Regards\'", "Comment 3: \' !screenshot-1! !screenshot-2! 30410200-B20\'", "Comment 4: \'Hello", \'Comment 5: the problem was a corrupted document in XL - !screenshot-3! After the repair\', "Comment 6: the VT-126/02 element has been linked with correct element order. Elements from VT-126/02 have been generated.Currently you need to confirm this WMR+ !screenshot-4! then you will have a stock and you will be able to generate a document for VT-145.\'", \'Comment 7: "{code:java}/**** Script for SelectTopNRows command from SSMS ***/SELECT top 100 FROM [DHCountry_DH_Sabac_Prod].[dbo].[VehicleTicketElementERPDocuments] where VehicleTicketElementId in(select id FROM [DHCountry_DH_Sabac_Prod].[dbo].[VehicleTicketElements] where vehicleticketid=\\\'AAA30761-BF08-4687-B1A8-308FE608D710\\\' )(select * FROM [DHCountry_DH_Sabac_Prod].[dbo].[VehicleTicketElements] where vehicleticketid=\\\'AAA30761-BF08-4687-B1A8-308FE608D710\\\' and ItemId=\\\'EA03FDE0-094F-40BE-9993-D1D98E25AA72\\\') SELECT * FROM [DHCountry_DH_Sabac_Prod].[dbo].[VehicleTicketElementERPDocuments] where VehicleTicketElementId in(select id FROM [DHCountry_DH_Sabac_Prod].[dbo].[VehicleTicketElements] where vehicleticketid=\\\'39BC4CCB-91F7-4B3F-89D5-0CCABF766DF0\\\'){code}"\', "Comment 8: \'wmr+ is confirmed. thanks\'", "Comment 9: \'You can close this ticket now. Thank you.\'", "Comment 10: \'Thank you for confirmation.\']"]\nRelated Issues:\n[]\n\n### End'}

Subsets and Splits