SYSPRO Application Designer: Customize Screens and Fields
syspro application designer
Also searched as
- syspro customize screens
- syspro add custom field
- syspro custom forms
- syspro user defined fields
Short answer
SYSPRO Application Designer is the tool used to change how SYSPRO screens look and behave without changing the core program: rearranging or hiding fields, adding custom fields and forms, and adjusting layouts for different operator groups. Customizations survive upgrades better than code changes but still need testing at each version change.
Applies to: SYSPRO 7 and SYSPRO 8; capabilities differ by version, so confirm in your release documentation
Customize a screen safely
- 1Confirm you need a customization: check whether a setup option, a security setting or a custom form already does the job.
- 2Back up the environment or work in a test company and test system first, never in live.
- 3Open the screen you want to change and launch Application Designer from the program, if your operator has the right to do so.
- 4Make one change at a time: move, hide, rename or add a field, then save the layout.
- 5For extra data, add a custom field or form, and decide whether it appears on documents or reports as well.
- 6Test with a user from the target role, not just an administrator, to confirm security and field access behave correctly.
- 7Document the change, then repeat the test after every SYSPRO update or version upgrade.
What it can and cannot do
Application Designer is a presentation-layer tool: it changes what an operator sees and can enter, such as which fields display, their order, labels and extra data fields. It is not a replacement for business logic.
It will not change core posting rules, costing methods or calculations. Where you need logic, such as a rule that blocks a sales order when a custom field is empty, you need a supported extension mechanism such as the SYSPRO business objects, triggers or an add-in built by a developer.
Custom fields and reporting
A custom field only helps if it can be reported on. Before adding one, decide how the value will reach reports, exports and integrations, and whether the SYSPRO reporting tools expose it. Otherwise the data sits on the screen and nobody can use it.
Keep a register of custom fields with owner, purpose and where they are used. After a few years, undocumented fields are the biggest source of upgrade surprises.
Upgrade and governance
Customizations made through supported tools are designed to carry forward, but screens change between versions. Retest every changed screen in a test environment, and keep screenshots of the intended layout.
Restrict who can use the designer. A change made by an unauthorized user can affect every operator in a role, so treat it like a code change with request, approval, test and release.
Try it here, free
SYSPRO Upgrade Checklist
A phased checklist for upgrading SYSPRO: scoping, backup, customisations, test cycles and cut-over.
Common pitfalls
- !Customizing in the live system with no test environment.
- !Adding custom fields no report or integration can read.
- !Letting many operators use the designer without change control.
- !Skipping retesting after SYSPRO updates.
- !Using a screen change when the real need is a business rule.
How an ERP-grounded AI assistant handles this
A SyteRay-style or ERPray assistant cannot replace Application Designer, but it can help around it: summarising which custom fields exist, drafting the change request and test script, and answering questions over the data held in custom fields once they are queryable. Keeping the model on-prem means customization details and documents stay inside your network.
Frequently asked questions
What is SYSPRO Application Designer?
It is SYSPRO's tool for changing screen layouts and adding fields and forms without editing the core program. It lets administrators or consultants tailor screens to a role. Availability and features depend on your SYSPRO version and licence.
Can I add a custom field in SYSPRO?
Yes, SYSPRO supports custom fields and custom forms through its customization tools. The field must also be exposed to reports or integrations to be useful, so plan that at the same time as the screen change.
Do SYSPRO customizations survive upgrades?
Supported customizations are designed to carry forward, but they are not guaranteed. Screens can change between versions, so retest each customized screen in a test system before upgrading production.
Who should be allowed to use the designer?
A small group of administrators or trained consultants working under change control. A change affects every operator in the role, so the same discipline as code changes should apply: request, approval, test, release.
Related
SYSPRO 7 to SYSPRO 8: What an IT Leader Should Plan Before Upgrading
A SYSPRO 7 to 8 upgrade is mostly a customisation, integration and report inventory exercise rather than a data migration problem. List everything that touches SYSPRO, test each item in a copy of production, plan the user interface change for operators, and agree rollback. Check with your SYSPRO partner and current support terms for your version before deciding the timing.
How-toHow to update SYSPRO (and how to check the latest version)
SYSPRO 8 ships as named releases (for example 2022 R1 style names) plus later updates, and the current release is listed on the SYSPRO partner and customer portals, not on a fixed public page. To update, back up, test the new build on a copy of your data, then update the server, services and clients in a planned window.
How-toSYSPRO API Documentation: e.net Business Objects and REST
SYSPRO's integration layer is e.net Solutions: a set of business objects (queries, transactions and setup objects) that take and return XML, reachable through a COM or .NET interface or through web services hosted by the e.net components. The documentation ships with the product help and the schema (XSD) files for each business object; a typical call is Logon, then Query or Transaction Post, then Logoff.
Error fixSYSPRO error: object reference not valid (or not set to an instance)
This is a .NET null reference raised inside a SYSPRO client component. Common causes are a client build that does not match the server, corrupted local settings, missing or damaged .NET components, or bad data that one program does not expect. Reproduce it, then test with a clean client and a different operator to isolate the cause.
How-toSYSPRO reporting API: e.net, SRS server-side reporting, Crystal Reports and SRS preview problems
SYSPRO gives you three reporting routes: the e.net Solutions business object API (XML in, XML out) for programmatic data, SYSPRO Reporting Services (SRS) for designed reports run on the server, and Crystal-based or SQL-based custom reports. If the SRS preview does not work, check the services, the runtime and bitness, the SQL permissions and the client and server versions in that order.
Error fixError validating SYSPRO online profile: what it means and how to fix it
A profile validation error means the SYSPRO client or service could not confirm the operator, company, licence or database connection it was handed at logon. Check the service and licence first, then the operator and company, then the database and disk, in that order. Storage errors are usually full disks, a locked SQL file or a tempdb problem rather than a SYSPRO bug.
AI for ERPAI for SYSPRO, Grounded in Your Own Manufacturing Data
Add AI to SYSPRO without moving your manufacturing data to a public model. On-premise and private-cloud LLMs for SYSPRO in Australia, NA, and beyond.
AI for ERPAI Agents for ERP, Running On-Prem
A practical guide to on-prem AI agents for ERP: what they can safely automate, where human approval belongs, and how to design the guardrails.
AI for ERPA Private LLM Grounded on Your ERP Data
How a private LLM answers questions on your ERP data: RAG plus text-to-SQL, role-based permissions inherited from the ERP, and where each fits.
Stuck on SYSPRO?
Talk to engineers who work inside SYSPRO every week, and who build private AI that answers these questions from your own ERP data.
Keep exploring
Free tools
- SYSPRO Upgrade ChecklistA phased checklist for upgrading SYSPRO: scoping, backup, customisations, test cycles and cut-over.
- SYSPRO MRP ChecklistA checklist of the master data, parameters and review steps that decide whether SYSPRO MRP output can be trusted.
- SYSPRO SQL Query GeneratorGenerate read-only SQL Server queries against common SYSPRO tables. Fill in database and filters, then copy the code.
ERP fixes and how-tos
- SYSPRO: Custom Form Fields, Activity Based Costing and GRNSYSPRO how-tos: add custom form fields to screens, approximate activity based costing with work center rates and overheads, and receive goods with a GRN.
- SYSPRO 7 to SYSPRO 8: What an IT Leader Should Plan Before UpgradingA practical SYSPRO 7 to SYSPRO 8 upgrade plan for IT leaders: inventory of customisations, integrations, reports, testing, cutover and when waiting is fine.
- How to Add AI to SYSPRO On-Prem Without Moving Your DataReference architecture for adding a private AI assistant to on-prem SYSPRO: SQL Server read replica, e.net business objects, retrieval, local GPU and audit.
AI on your ERP
- AI for SYSPRO, Grounded in Your Own Manufacturing DataAdd AI to SYSPRO without moving your manufacturing data to a public model. On-premise and private-cloud LLMs for SYSPRO in Australia, NA, and beyond.
- AI for SYSPRO production and job costingHow AI reads SYSPRO WIP jobs, labor and material postings to explain job cost variances and late work orders, with read-only access and on-prem hosting.
Integrations
- How to use ChatGPT with SYSPROHow to use ChatGPT with SYSPRO: exporting data vs live access, custom GPT actions over a SYSPRO API, enterprise data controls, and when a private model is better.
- How to add AI agents to SYSPROHow to add AI agents to SYSPRO: tool layer over e.NET business objects and SQL Server, MRP exception triage, PO expediting, human approval before any posting.