DACS | Domain Adaptation via Cross-domain Mixed Sampling | Speech library

I think you want something more like this to process multipage TIFFs. I have tried to improve your variable names from nondescript names like data, var to make it more readable.

The BACPAC file and method you are using is not fit for your purpose.

A BACPAC is a snapshot of the data, and doesn't contain any information that will allow you to restore back prior to the moment the BACPAC was created. BACPACs are useful for transferring copies to on-prem servers, Devs for bug analysis/development or moving databases between versions of SQL easily but are not a backup solution.

See here for more information about, and common uses for BACPAC/DACPAC files.

In the context of an Azure SQL database (either single database or pooled) the concept of transaction logs as you know it has changed. In the modern context the need to restore back to prior moments in time is covered by the PiTR and LTR backup features found in the Azure Portal.

PiTR (or Point in Time Restore) gives you the ability to restore a database to any millisecond in time up to 31 days in the past (depending on configured settings per database). I've used this many times and the hardest part is converting UTC (which the Azure Portal works in) to the local time you need your database restored back to.

LTR (or Long Term Retention) backups give you weekly, monthly or yearly options for saving backups. Here is a good MS Doc article on the subject that states:

When you restore a database from an LTR, the service determines which full, differential, and transaction log backups need to be restored.

We've had well over 100 client databases on Azure SQL for about 3 years now (mix of single databases and elastic pools) and we've never come across a restore request that we couldn't cater to. The 31 days of PiTR really is a killer feature.

UPDATE This is where you go to view what LTR backups are available for a specific database:

Go to the database in question in the Azure Portal, go to Data Management -> Backups blade, and click Manage next to the database you want to view. You'll see something like this that should reflect the LTR backup configuration you have for that database.

Ive also since found this link to an MS Docs article that states:

Note

You can use SQL Agent jobs to schedule copy-only database backups as an alternative to LTR beyond 35 days.

This might be useful in helping you get the configuration you need to fit the requirement.

I am not 100% certain, but I think this is about the ID's in the ASPX rather than the database data. For example:

Notice ID="PXLayoutRule1" in that sample. If this "ID" value of any entry in the ASPX is duplicated anywhere in the screen as an ID of another entry, you will get an error.

I had similar issues in an earlier version, especially when I would try to customize a screen and have the customization screen interface crash on me in the middle of it. I'd try deleting the screen, but I'd get orphaned files in the CstDesigner and CstPublished folder, which would really compound my issues.

Hopefully, you know how to look through your ASPX file and the Customization Project XML to check all the ID's. If you do know how to walk through all that, just add something to all of your ID values, like an X at the end. (i.e. PXLayoutRule1X) If not, gaining that familiarity is a worthy side-objective as you continue on.

If your issue is the same as I had in the past and you cannot simply find and edit the duplicate ID in the ASPX file or Project XML, here are some steps to take AFTER you backup your project and the affected folders noted in these steps. And, of course, this also assumes you are working in a development copy of your instance. (I often clone my main DEV instance to my laptop to test things like this if I am unsure so that my DEV instance stays unaffected. It just takes extra time you may or may not have.)

1. Delete the screen from your customization project.
2. Locate the folder CstDesigner and CstPublished under your instance's root folder (i.e. AcumticaDEV, Sandbox, etc. where your site exists)
3. Go into the Pages_XX folder (where XX is the 2 character code for your 1st 2 letters of the screen ID)
4. Delete the screen file(s) from there, if you find them.
5. If this is a custom screen, go into the Pages folder which is located in the same root folder of your instance as those folders in step 2 and repeat steps 3 and 4 in that folder.
6. Check for any reference to your screen in the Project XML from the file menu in the Customization Project screen and remove those sections if they exist. (This tends to relate more for customizing an existing screen.)
7. Publish your project.
8. Start over on your page and see if you still get the error.

Again, be sure to get a backup before taking these steps so that you can easily put it back if that does not resolve your problem.

Going top-to-bottom, you have your application code which in the end will likely want to talk to some server: resolve DNS name, open a tcp connection etc. This is what LwIP provides - a set of API functions: socket functions, DNS functions and other. For example, when you do a TCP socket connect to a given IP address and port, it decides which out of available network interfaces to use, constructs a frame in form of array of bytes and sends those bytes over that interface. This is where LwIP part ends - it requesting given network interface to output X bytes it provides, as well as consuming any bytes that may arrive on that interface. It doesn't know how exactly to make the bytes "come out", but it knows how to construct the data to send and understands the data you give it.

Going bottom-to-top, you have your modem - LTE, 3G, 2G, doesn't really matter. Modems provide a set of AT commands to talk to them to perform a set of functions: set SIM card PIN, get signal quality, list available operators, select an operator etc., as well as a way to switch it to PPP mode, which also done ATD command. Assuming the modem has been configured properly before, once you switch it to PPP mode it'll be able to send data using PPP protocol and will also "spit out" any data it receives. This is where the modem part ends - when switched to PPP mode, the modem is able to send and receive raw network traffic using PPP protocol. It knows how to output the raw bytes you give it, but it doesn't understand them on a very high level.

Your role is to connect (interface) both parts. Your modem uses PPP to produce and consume network traffic. LwIP has the capability to understand and produce PPP frames.

In case of sending data out, after preparing a PPP frame LwIP is going to call the sio_write function that is expected to send provided bytes to modem that's already in PPP mode. This is the part that you need to fill in. In case of reads sio_read is used and it's your job to fill it in so that it returns bytes that were received from the modem. How you're going to do that - using RTOS and queues for bytes, no RTOS or any other way - doesn't matter. It's what you find more convenient or what fits your overall project structure better. As long as those functions do what they're supposed to, LwIP will be happy to use them.

This interfacing is discussed in more detail here: https://lwip.fandom.com/wiki/PPP#PPP_over_serial. Again, the general concept is that LwIP is just a software library and in the end it'll want to send and receive bytes. Your job is enabling it to do so, by filling in the functions it expects.

An alternative solution could be to have a reusable attribute that you can attach to any field. I think this is cleaner than adding logic directly in the Data Access class...

I copied below from my method which pushes files from an Opportunity to a Service Order. Also I adapted in order to act on ARInvoice & Service Order. You may adapt it for your situation. In graph CreateInvoiceBase, there is a method named CreateInvoices. See if you can use the injection routine below, and extend/override CreateInvoices, or a related method in that graph.

You can create a setup screen with a checkbox that will control whether you have the feature enabled. In the screen create a PXSetup View and in the constructor check the flag for activation. If it's not active throw a PXSetupNotEnteredException. This will blank the page and give the user a message of your choosing.

You need to decorate the custom entity DAC with PXPrimaryGraph attribute and pass the maintenance page graph type in parameter:

In this case, you are looking to update values from the DAC CSAnswer with information from the DAC INItemCost. It is my understanding that PXFormula[] attribute can be used to update values from the same DAC record, and/or for aggregated calculation.

Typical example: A grid's Unit Price and Quantity are used to obtained Extended Price (values from the same DAC record). And that result is updated in the document's total (aggregated total) I have not seen it being used in an example like yours.

I was able however, to update the value with this alternative approach: