Hello Chris,Just to ease your concern about missing orders during the transfer from active tables to history tables due to network issue. Order information will never be deleted from active table until the end of the successful transfer. We had cases when transfer was interrupted and order was partially moved to history, fully moved to history but was not removed from active table, etc. So, in such cases sometimes the order is not visible on Server Order or Service Order History search screens but should be visible on Order locator search which looks at both active and history tables. And it’s definitely can be found directly in the database in one of the tables (active or history) or both.
Hello Andrei,It seems you posted in the wrong group forum. This is Alliance product group forum so we will not be able to answer your question.
Hello Chris.Just a note. There should be another option like hide/invisible just to avoid questions like why the option is disabled for me and how to enable it.
Just a note. It’s built in functionality of Web browser and works for any link on any page not just links in Alliance.
If steps Reid described not followed there will be no record in product_person_xref table and that may cause the error. Issue can be resolved by deleting/recreating vendor. Thank you,Mark
Phil is correct. The fix corrected import/export bug for Web interface views and included in 15.4 SU4 but that affects only organization views.
Hello Robin. Location for GlobalXMLLocation.txt. For any version this file is in the folder like ..\Astea Alliance 15.0\Bin\Framework\
Hello Christophe,From what I could see in the code the change is in SU4 and we suppose to get SU4 in a few days. This change is not for any specific file extension but the fix for the issue when new extensions added to Global.xml and they are not recognized.
They will, I’m sure of it.
Sorry, forgot to add .cfg.
Hello Christophe,Actually it’s a little bit more than that. Those DLLs below need to be modified.It will be available in 15.3 HF7. And I just tested your API and it works fine in modified 15.3 HF5. Is it what you expect?This file is part of <install_path>\Bin\External\Integration Center\Api\Xml\data - new_SO_with_attachment.xmlNOTE: The binary file data should be passed to API as base64String formatThe C# code examplebyte[] fileData = File.ReadAllBytes(@"C:\temp\some_file.doc");string strData = System.Convert.ToBase64String(fileData);
Hello Kyle.I think, if I remember correctly, the patch will overwrite that config file and you need to make manual changes again.
I would agree with Phil that manual changes are risky. Also, you may need to check and verify your changes after every upgrade as they can be overwritten by the installer.
Hello Leann,This custom field is not in our TFS files , but it’s all over the place in customizer including history folders, please see below some sample of it. I installed customizer files and there it is. I took a look at Sales Order and was also able to reproduce the issue. I’ll look for the cause and let you know. Thank you,Mark
Hello Leann,Have you tried conflict resolver after import?
Hello Leann,I think you need to publish them in UAT and create an export for customizations. Then you will need to import them in production. I’m surprised you can see Dev changes in production but I can be wrong.Thank you,Mark
Hello Leann,Could you please name few of those modules where you have that issue? I tried to reproduce it in the stage environment and everything looks fine. In production environment I had no errors on several modules but I had a different DDLB error on Order Locator module that points to missing in DDLB cst_drop_down_test. As it’s not in TFS, I assume it’s somewhere in customizer files. Could you please try to run Conflict Resolver one more time? Thank youMark
Hello Chris,The reason behind having this button on Resolve tab is to improve performance of the system from what I can see. Otherwise every time you open Resolve tab it would recalculate prices, looking for changes in labor, materials, services, etc. and that may take some time depends on the order. And if you are going back and forth just to look or verify other tabs you don’t need that calculation every time. It will be triggered of course when Invoice clicked but that’s expected. By the way there are some improvements in the latest versions how field quote prices handled.Thank you,Mark
As another note, if the main version of upgrade is not there then you can add it to the list in Software Version column in the format like14.0.0.27 at the same time. The rest of the columns on this screen will be populated automatically. After that new version number can be used to set Astea Resolved Ver. field on all other tickets that belong to that release/shipment.
And we usually put the max value of 86400 in Session Timer just to be on the safe side that the session will not expire unexpectedly.
I can confirm that there is no visual representation for this field in any recent versions and up to the latest version of Alliance.
Yes, this is a correct ID value for v. 15.1.
@ZTC ZTC JGOTA You can try to search on the main page https://community.ifs.com/ to find similar postsor try to find the correct group on https://community.ifs.com/groups. And, I think, you have to post it again. Not sure if you can just change the group for the post.
Hello,It seems that you posted your question in the wrong group. The screenshots does not look like Alliance screens. Sorry about that.
It also affects currency settings if there are differences in currencies between countries. But the main difference is date and time formats as Phil and Reid described.
Already have an account? Login
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.
