I have created customization which has 4-5 different tabs and each tab has various groups. Customization is for Stock Item screen (ScreenId - IN202500). I have set all its required properties such as StartColumn=True, StartGroup=True, GroupCaption, etc. However, when I am in Import Scenario (System > Integration > Manage > Import Scenarios) for Stock Items and want to map these new fields, it is NOT showing different groups for all tabs such as
Tab1->Grp1
Tab1->Grp2
Tab2->Grp1, etc.
Instead it is showing all fields in single object under Tab1->Grp1->.
I found the solution. All fields has to be created under FormView tag and then Column and Group. Hence it will display these fields in Import Scenario.
Related
currently I'm trying to import approx 1600 tasks from Azure DevOps Kanban board to another one (via browser). I've faced two problems by doing this:
It is not possible to import the task with Closed Date field, it says:
Value of a readonly field Closed Date was modified. Please revert the Closed Date values or remove the column from the input file and and try to import again.
Removing the column with "Closed Date" will cause issue with default state "Done", it says:
The field 'State' contains the value 'Done' that is not in the list of supported values.
I've copied (manually) the project settings from old Organization to new, such as:
Process \ State (and assigned it to the project):
Time and Locale as it was set in old Kanban
Also, I had to remove the ID column, because it caused the issue:
Still it is not possible to import all these tasks because of the issues. I'm looking for any tips how to fix this.
Below there's an example of CSV:
Work Item Type,Title,Created By,Created Date,Assigned To,State
Issue,Some test task number 1,TestCreator,02.06.2020 15:19:24,TestWorker,"Done"
Issue,Some test task number 2,TestCreator,02.06.2020 15:20:23,TestWorker,"Done"
When importing work items via CSV file in Azure DevOps, first make the following statements are true:
1.The source project to export and target project to import has the same work item type configuration, in common, they need to have the same process configuration, for example, work item type, state.
2.All work items you import are created in a new state. This rule means that you can't specify field values that don't meet the field rules for the new state. (That's why "Done" that is not listed as supported value)
3.Make sure you don't assign IDs to new work items that you're adding. Work item ID is unique in one Azure DevOps organization. (ID will cause the following error message)
With the above prerequisites, the import process loads the imported work items into the queries view in an unsaved state. No IDs are assigned. Verify the results are what you want. Then, choose Save Items to save the work items.
If you still get the error when importing, try reduce the work item counts for per import attempt. As you said, you have approx 1600 tasks, you could import by separating them into several queries.
I have two GI screens, which takes CustomerID as input and show data from different screens. My question is, I want to create a custom screen and add tabs Sales Orders, Invoices, and want to display that GIs data in these tabs. The main purpose is instead of checking data in multiple GI screens want to display all information on one screen.
I have one ways maybe it can help, but i'm not sure.
First, you create virtual view like usrGI_CD or GI_CD in CacheExtension<GI-DAC>
Next, you handle it in your code like:
GI-Graph graph = CreateInstance<GI-Graph>();
GI-DAC giResult = PXSelect<GI-DAC, Where<Field1, Equal<Required<Field1>>>>.Select(graph, valueField1,......);
You can add a lots field you want same with Field1. After that you will have row of value that you want and you can use PXUIFieldAttribute.SetValue(cache, giResult.value) to set value in your DataView.
Hope this help!
I have been extending Acumatica screens by adding new fields accordingly. However, for this particular scenario, I want to create a new tab in the Cases screen.
This tab would include a list of items. These list of items would be a custom table that I will be adding to Acumatica.
Is this possible?
And is this the correct list of Steps?
1. Create table in Acumatica for the list of items
2. Create DAC for the new table
3. Extend the Cases Graph and add a new Data View (i.e. PXSelect)
4. Edit the Cases screen so that a table and grid are added accordingly
5. Link the grid to the Data View through the Data Member property
I am not sure whether you would also need to implement some additional events, but I believe that if the DAC has the correct link to the Case and the correct attributes ... it should work.
Would be much appreciated if someone helps to confirm the above approach please.
Adding a tab page containing a grid bound to a DataView on a custom DAC in the case entry screen is a supported scenario.
There are a few ways to do it. Whether you are working on a Customization Project or an Extension Library will influence how you approach this requirement.
Your steps seems all right. Here's how I would do it in a Customization Project:
Create a new table in the database using a DB management utility (ex: SQL Server Management Studio). Restart WebSite instance or IIS to make sure Acumatica picks up DB schema change.
In DB script section of the customization project, add the new table and check import table schema from database. This will ensure publishing the customization project will create the table in the database.
Create a new DAC for the new table, DAC name should be the table name.
Extend the case entry graph (CRCaseMaint) and add a new DataView on your DAC.
Edit the case entry screen (CR306000), add a TabPage and a grid.
Bound the new grid to your DataView using the DataMember property
I have created a bunch of NetSuite Entity Fields through the UI (Customization > List, Records & Fields > Entity Fields > New) in one of our two NetSuite Sandbox instances.
I now need to recreate those same fields in our other sandbox, and then eventually in production.
Rather than input them by hand every time, I'd like to either export/import them, or, script them. Unfortunately the information provided by NetSuite doesn't seem to cover this (if it does it's very hard to find). For example, the Import CSV functionality doesn't seem to cover Entity Fields, and the "SuiteScript Supported Records" documentation (for 1.0) doesn't seem to cover them either.
Is it possible to export/import Entity Fields either via CSV or script?
The way to do this is by creating a 'SuiteBundle' that packages your customizations, which you can then share with other accounts.
You can view the documentation here (Netsuite login required).
I have tried the liferay-ui:search-container to fetch and display the database table records on UI in a table/grid format. By using the liferay-ui:search-container I am getting the output as shown below,
I am fetching the USER_ table records in the above screen shot.
Problem:
I wanted to make the grid columns dynamic like, I wanted to enable an option for end user to remove the unwanted columns and add the wanted columns in the respective grid/table.
EX:
In the above screen shot the the following columns are showing in a grid.
First Name, Last Name, Screen Name, Job Title, Organization, User Groups
Now If user wants to remove Job Title and wants to add Greetings and Mail Address columns on UI with click events with out touching/ modifying the code.
How can I implement this feature?
Note:
I need to implement this feature for custom models.
Queries:
1) Is there any api/methods to implement/enable this feature?
2) If not how can I do implement the steps? Any suggestions or steps to achieve this task?
This can be achieved by adding a configuration page to your portlet.
You can develop portlet configuration page which can have required options to be configured and save as portlet preferences.
Later on while displaying the search container you can retrieve the portlet preferences and display only those columns which were selected in the configuration form.
Here is a link on how to develop the portlet configuration using portlet preferences: Implementing Configurable Portlet Preferences