Hi @bdoucette , If you are starting with IFS Cloud related developments, there are various courses offered by IFS Academy. I will list them down with the areas of expertise, the duration, and the objective/purpose of the course. Course name Objective Duration Base Server Development for Application Core - IFS Cloud Introduce IFS architecture and tools (IFS Developer Studio) of the server-side developments. 5 sessions (each session is 4 hours/day) IFS Aurena Development - IFS Cloud Introduce to IFS architecture and developing middle-tier artefacts and frontend IFS Aurena pages (using IFS Developer Studio) 8 sessions IFS Report Designer Development - IFS Cloud Introduction to IFS Cloud reports architecture, tools to develop reports and the report development process 4 sessions Integration API Development - IFS Cloud Introduction to IFS integration platform, development tools (IFS Develo
Hi @MitDenukN , Additional to the steps mentioned in the previous answer, you can check below criteria, if the custom attributes are not showing up. Make sure the system parameters for custom object framework and custom page framework are turned on.You can check this by opening the “System Parameter” page and searching for parameters with category “Custom Objects”. There, you will find 2 parameters “Custom Attributes framework” and “Custom Pages framework”. Make sure both the parameters are “ON”.Make sure that you have added the attribute to the correct entity.In this case, it should be “InventoryPartInStock”.Make sure the added custom attribute is “Approved” and “Published” Make sure the “InventoryPartInStock” Entity is “Approved” and “Published”Make sure that the UI element that the attribute is adding to is correct.In this Case, it should be “InventoryPartInStockList”. ( I can see that this is correct in the provided screenshot). I believe most probable cause for the issue might be
Hi Haveesha, There can be several different reasons for custom fields to be not shown up in the page designer. Make sure that you added the custom field under the correct entity that the page is connected to.You can use the debug console -> Page info tab to verify this.Make sure the custom object is approved and published Try refreshing oData cacheTry refreshing the OData Cache: [main|b2b] /ifsapplications/projection/ClearCache?METHOD=CLEAR_PROJECTION_CACHE&VALUE= [*|ProjectionName**] Try refreshing “Mapping cache”You can do this by opening the user context menu “Caches -> Clear Mapping Cache”Make sure to select the correct UI element (group, list) when adding the custom field to the screenYou can refer to below section on the ifs documentation as Dilini mentioned in earlier answer. https://docs.ifs.com/techdocs/22r2/040_tailoring/225_configuration/200_client_configurations/150_attribute_configurations/
Hi Teshan, Chethana, I haven’t come across this exact issue before.The most common cause for the initialization hang issue is the mobile database is not getting downloaded to the mobile from the mobiledb location. However, according to the information provided on the error this would not be the case. Have you tried checking below points.Check the mobile error log in the server sideCheck for potential communication errorsCheck the server logIncrease the communication log level and check for potential errors.Check the “DownloadUrl” on the mobile web.config file on the mobile service on the server Check if there are mobile customizations related to IOS client (initialization) and check for potential issuesSimilar issue was reported on below post. You can further check the suggestions from Brian on the below post. https://community.ifs.com/ifs-field-service-management-fsm-employees-partners-only-103/fsm-mobile-initializing-without-ending-16033
Hi,It is not possible to make custom adjustments to place a button in a specific position in the screen. The screen will be rendered on the runtime and UI elements such as fields and buttons will be placed based on the underlying design metadata. The FSM Mobile UI Designer only allows changing the order of the button elements appearing on the screen using the “Field Order” screen.
Hi @Hasara Dinu ,When there is an error occurred in inbound integration, the parent and child records gets rolled back. When there is any error occurs in tasks, it should roll back the request record (assuming request is getting created with the same integration).However, it will not rollback records in the associated tables. As an example, since place has an associative relationship, it would not rollback the place record even if an error occurs in task/request. The modification occurs on the place table will be executed on a different transaction.
Hi @Hasara Dinu ,I think T-Tables will be a better option in this case. T-tables can be used in order to import data from a table on an outside system to FSM.Any table in FSM has related T-table starting with “T_”. The data from the external table has to be copied to the relevant t-table. Once data copied to T-table, it can be seen from the T-table editor.Next, the entries in the T-table can be added to the actual table by using import functionality (perform_import_from_t_table). You might be able to create a scheduled process to import from t-table. You can refer to below post for more details.https://community.ifs.com/troubleshooting-310/how-is-the-t-table-editor-used-3292
Hi Dulshan, Although it is technically possible to either create a separate Sync Rule for the new custom entity or to add it to the existing task Sync rule, the 2 approaches will result in different behavior. First, lets see what happens if this is added as a separate new Sync Rule. The Sync Rule can be added as either a real-time or batch (batch-All, batch-delta) depending on the required sync behavior. Since this entity is related to the task I assume changes to this table need to be synced real time, thus a real time Sync Rule is needed. If a new sync rule is created, every time a record in this new table gets added/ updated/deleted, the changes would sync to the mobile. However, since its added as an individual Sync Rule, when an existing task gets assigned to the mobile user, it won’t sync the related records of the new custom table. Means that, it will only sync the records from new custom table, only if a change occurs in that record.Secondly, if the new table is added to the ex
Already have an account? Login
No account yet? Create an account
Enter your username or 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.