peterbruce
Legendary Poster
JDEList,
This is all in development (CRP/PY and DV).
I have a custom application that does a lookup on a custom table. I had to add a column to the table some time ago, so I deleted the fetch single event rules and created new ones. Everything was working fine for a number of weeks and many changes to the application, until I made an unrelated change. Now I get the mismatch on the web client, but not on the fat client local web. The log from the server manager shows the physical columns (table prefix with data dictionary alias) missing the column I inserted and the logical columns (just the data dictionary alias) with all the columns.
Clearing Enterprise server and JDBJ caches did not help. Bouncing the JDE services on the enterprise server did not help. Removing the 6 .ddb and .xdb files did not help. I checked out/in the table rebuilt and deployed the package, all with no affect.
I am at a loss as to what to do next. It had crossed my mind to create a whole brand new table.
The custom table is only used in the is application and the associated UBE. It is manually maintained in the database, though there is no anticipation for much change. The application is in production. This project introduced the table, so the table is not in production.
Once this is fixed the project is ready for UAT. But at the moment that is not possible because this error prevents the application from processing properly.
This is all in development (CRP/PY and DV).
I have a custom application that does a lookup on a custom table. I had to add a column to the table some time ago, so I deleted the fetch single event rules and created new ones. Everything was working fine for a number of weeks and many changes to the application, until I made an unrelated change. Now I get the mismatch on the web client, but not on the fat client local web. The log from the server manager shows the physical columns (table prefix with data dictionary alias) missing the column I inserted and the logical columns (just the data dictionary alias) with all the columns.
Clearing Enterprise server and JDBJ caches did not help. Bouncing the JDE services on the enterprise server did not help. Removing the 6 .ddb and .xdb files did not help. I checked out/in the table rebuilt and deployed the package, all with no affect.
I am at a loss as to what to do next. It had crossed my mind to create a whole brand new table.
The custom table is only used in the is application and the associated UBE. It is manually maintained in the database, though there is no anticipation for much change. The application is in production. This project introduced the table, so the table is not in production.
Once this is fixed the project is ready for UAT. But at the moment that is not possible because this error prevents the application from processing properly.